[server][vpj][controller] Remove Kafka serialization classes and improve producer flexibility

[sushantmane]

Remove use of org.apache.kafka.common.serialization classes and update producer for easier parameter addition

Changes:

Kafka Producer Adapter Enhancements

• Deprecated the old create method and introduced a new default create method in PubSubProducerAdapterFactory.java using PubSubProducerAdapterContext.
• Modified ApacheKafkaProducerAdapter to use byte[] for keys and values instead of KafkaKey and KafkaMessageEnvelope.
• Added a new sendMessage method to improve flexibility.
• Updated ApacheKafkaProducerConfig to include PubSubMessageSerializer and set serializer configurations for Kafka producer.

Configuration Management Improvements

• Removed unnecessary deserializer configurations from getPubSubConsumerProperties in DumpAdminMessages.java.
• Updated configuration prefixes in PubSubConstants.java to use PUBSUB_CLIENT_CONFIG_PREFIX.

Code Cleanup

• Removed SharedKafkaProducerConfig as it is no longer needed.

How was this PR tested?

Does this PR introduce any user-facing changes?

• No. You can skip the rest of this section.
• Yes. Make sure to explain your proposed changes and call out the behavior change.

[ZacAttack]

This looks ok aside from the test failures.

com.linkedin.venice.exceptions.VeniceException: Broker address must be provided to create a pub-sub producer

^^ I think if you just patch that all the failing cases will pass

[FelixGV]

Just some high-level comments...

1. I think for the server/DVC code, it is almost certainly a good idea to use byte[] and let us control the serde on our own. This will open up some new opportunities for optimization.
2. I think the current API where we can interact with the pub sub via POJOs is probably useful in the rest of the code (e.g. controller certainly, possibly VPJ as well).

So rather than making the old API deprecated, can we just support both? It might make the size of this change smaller as well...