Discussion: relax version constraint on Confluent.Kafka in a future major version?

[njlr]

From #96 (comment)

[bartelink]

@deviousasti @enricosada As mentioned in the linked thread, it appears that a 2.0 that targets Confluent.Kafka 2.x without pinning might be the best way to let FsKafka do its job without there being a need to have regular releases as a knock-on effect of individual Confluent.Kafka releases, as there's clearly no release impetus coming organically from the consumers that established this policy in the first instance?

If there's no response here, that's my plan (I don't intend to do the actual PRs myself)