updating to brod 3.16 and new kafka resp schemas

[jeffgrunewald]

Restructure the create, list and delete topic API to allow updating to brod 3.16 which migrates to a new structure for the underlying kafka_protocol response schemas which underwent a substantial change from the previous brod <= 3.14 versions.

Also cleans up the now-deprecated :crypto.rand_uniform/2 API in the random partitioner in favor of the new :rand.uniform/1 function.

[tpitale]

🎉 shall I close the other PR #99?

[jeffgrunewald]

🎉 shall I close the other PR #99?

Sure; thanks for pointing out the changes there as they weren’t handled in the same location as the other kpro schema changes. And no, I don’t think we’re super concerned with maintaining complete backward compatibility; I think a a good majority of kafka users are likely using some form of managed kafka and thus keeping up to date so rolling the brod/kpro version forward as well seems reasonable and the alternative was going to make the version handling in the Topics module pretty messy and potentially reduce throughout because we’d have to add more round trips to query the api version to know how to handle each request. If you look at kpro’s different schema versions there’s absolutely no consistency between versions for any given req/rsp api.