fix: logging initialization for kafka consumer generated code

[sancheet230]

Description
This PR addresses a critical issue with logging in the generated Kafka consumer code. Previously, calls to logger.info(...) were made without a properly defined logger, which would cause compile-time errors. The fix introduces a standard logger initialization in the consumer declaration:

private static final Logger logger = Logger.getLogger(YourConsumerClass.class.getName());

This change ensures that all logging calls have a valid reference, aligning with Java best practices for logging. While this PR resolves the logging issue, please note that placeholders like recordFailure(ex) and the reference to ch (used in the consumer constructor) are still present and will need to be addressed in subsequent updates

Related issue(s)
Fixes #241

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sancheet230]

@AGurlhosur @dalelane @dan-r @KieranM1999 @lewis-relph @asyncapi-bot-eve Ready for review

[dalelane]

Can you explain what compiler error you're trying to solve, please?

As I understand the current intent behind the code, the logger is provided in the superclass. While I could perhaps see an argument for having separate loggers for every class rather than sharing, that's rather more subjective than the critical compile error you seem to be seeing.

[dalelane]

... I could perhaps see an argument for having separate loggers for every class rather than sharing ...

Further to that, if we go with a separate-loggers approach, I think it would be better to do that across the board (i.e. what about producers) rather than just for the one isolated example.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️