Fix: Make Airbyte connection fields properly labeled in Airflow 3

[Zeglow]

• Add proper relabeling for Airbyte-specific field meanings
• Ensure 'login' displays as 'Client ID' and 'password' as 'Client Secret'
• Similar pattern to other provider fixes

Closes #55841

---

^ 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 prek-hooks 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

[jedcunningham]

Hi @Zeglow, thanks for the PR!

In the future, when looking for issues to work on, please note whether the issue is already assigned to someone - that person has raised their hand to work on it and may be actively working on it already. If it's been a while since the assignment, you can always ask in the issue if they still plan to work on it - that is completely fair. Hope that makes sense. Thanks.

[Zeglow]

Hi @Zeglow, thanks for the PR!

In the future, when looking for issues to work on, please note whether the issue is already assigned to someone - that person has raised their hand to work on it and may be actively working on it already. If it's been a while since the assignment, you can always ask in the issue if they still plan to work on it - that is completely fair. Hope that makes sense. Thanks.

Hi @jedcunningham, thanks a lot for pointing that out! This is actually my first time contributing to an open-source project, so I really appreciate the guidance. I’ll make sure to check in the future. Thanks again for the reminder — I’m excited to keep learning and contributing : )

[jedcunningham]

No problem, welcome to the community 🍺

[jason810496]

Nice! Thanks for the PR!

The static check CI still need fix:

# install prek
uv tool install prek 

# fix the formatting 
prek ruff --all-files && prek run ruff-format --all-files

[jason810496]

nit: How about just assert the whole field_behaviour with dictionary? Maybe it be more straightforward for the test case.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.