Fix max_messages warning of Kafka ConsumeFromTopicOperator

[nguymin4]

The current logic of ConsumeFromTopicOperator is that :param max_messages: defaults to None implying read to the end of the topic.

But if the max_messages=None, we also have very misleading warning log e.g. max_batch_size (1000) > max_messages (True). Setting max_messages to 1000

This warning log contradicts with the current logic and in fact, we also don't set the max_messages to max_batch_size either.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[jason810496]

Thanks for the PR.

IMHO, instead of removing the warning, we should fix this part

airflow/providers/apache/kafka/src/airflow/providers/apache/kafka/operators/consume.py

Lines 100 to 107 in d517c63

	self.max_messages = max_messages or True
	self.max_batch_size = max_batch_size
	self.poll_timeout = poll_timeout
	if self.max_messages is True:
	self.read_to_end = True
	else:
	self.read_to_end = False

by making the self.max_messages attribute still int or None instead of ambiguous with bool ( also have to check the further usage of self.max_messages logic and adopt with this type change if needed ).

[nguymin4]

@jason810496 Sounds ok to me if we want to go that way. I now changed the logic of max_messages so it is not casted to bool anymore.

[jason810496]

Thanks for the change!

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.