Add config param to pass additional parameters to confluent-kafka-python

[kumaranvpl]

Description

• Add config param which needs to be passed to confluent-kafka-python
• Remove ssl_context
• Raise SetupError if ssl_context is passed
• Use TypedDict for config
• Remove unused params from Async wrapper which are added to maintain feature parity with AIOKafka implementation. This is not needed anymore.

Fixes #1405

Type of change

Please delete options that are not relevant.

• Documentation (typos, code examples, or any documentation updates)
• Bug fix (a non-breaking change that resolves an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a fix or feature that would disrupt existing functionality)
• This change requires a documentation update

Checklist

• My code adheres to the style guidelines of this project (scripts/lint.sh shows no errors)
• I have conducted a self-review of my own code
• I have made the necessary changes to the documentation
• My changes do not generate any new warnings
• I have added tests to validate the effectiveness of my fix or the functionality of my new feature
• Both new and existing unit tests pass successfully on my local environment by running scripts/test-cov.sh
• I have ensured that static analysis tests are passing by running scripts/static-analysis.sh
• I have included code examples to illustrate the modifications

[kumaranvpl]

@Lancetnik Points to discuss

1. I am removing ssl_context because it is causing confusion and confluent-kafka-python can't use ssl_context directly. It uses separate individual security params. Shall I raise error if ssl_context is passed ? - https://github.com/airtai/faststream/blob/pass-config-to-confluent/faststream/confluent/security.py#L16

2. Confluent kafka python accepts huge list of config mentioned here - https://github.com/confluentinc/librdkafka/blob/master/CONFIGURATION.md. To make users' life easier we have added some of those config as producer/consumer params, rest can be sent as part of config dict. When we are merging params and config dict which should take precedence? params or config items? - https://github.com/airtai/faststream/blob/pass-config-to-confluent/faststream/confluent/client.py#L151

[Lancetnik]

@kumaranvpl your decision looks good to me, but I have some notices:

1. We should raise RuntimeWarning if user setted up ssl_context option in parse_security method instead of suppressing it

2. We should create a TypedDict for config option to make it auto-compliteable and much explicit. Also, it should solves problems with another init parameters conflict (but the current merging priority looks good too)

[Lancetnik]

I think, we should use SetupError instead of basic ValueError in wrong broker parameters case

[kumaranvpl]

Noted. Thanks.

[Lancetnik]

Lgtm, I think, we can release it