Refactor: Directly pass HttpOperator data and json arguments to requests and aiohttp params

[gazev]

related: #37291

Both requests and aiohttp deal with json and data arguments in the same
manner (https://requests.readthedocs.io/en/latest/api/#requests.post and https://docs.aiohttp.org/en/stable/client_reference.html#aiohttp.ClientSession.request), so it would be more transparent to simply pass these arguments
directly. I believe it is also a good choice to be transparent in this
direct usage because requests is a very popular HTTP library so most
people already know how these arguments are expected.

The params argument could also be introduced in the HttpOperator with the same goal.

This PR was meant to address #37291 after seeing the discussion started here #37293 (comment)
The PR includes a breaking change.

[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: [email protected]
  Slack: https://s.apache.org/airflow-slack

[gazev]

@potiuk I opened the PR because of this discussion #37293 (comment) but hadn't realized you said a breaking change would not be ideal. What should I do with the PR? Thank you!

[potiuk]

Does the other PR fixes the same thing? If so - close it. If not - change yours to add new things. Why do you need to ask me :) ? Seems pretty straightforward?

[gazev]

Does the other PR fixes the same thing? If so - close it. If not - change yours to add new things. Why do you need to ask me :) ? Seems pretty straightforward?

I am really sorry for the inconvenience, I hadn't realized the breaking change was implemented in the mentioned PR.

[potiuk]

No need to apologise :)