vertex ai training operators: add display_name to rendered fields

[WSHoekstra]

---

Add display_name and model_display_name to list of rendered fields for Vertex AI operators.

[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

[potiuk]

For the future - you can add "Closes: #ISSUE_NUMBER" to the commit message and it will automatically link the issue you created and it will close it - saves a lot of duplicated effort.

Also - for such things we do not really need an issue - just open PR and add description what it does - we do not really like overhead and unnecessary beauracracy 😄

[shahar1]

Thanks for your contribution!
There was a static check error due to current limitations of the validate-operators-init static check: the templated fields should be defined in the constructor's signature and explicitly assigned via super().__init__(param=param, ...) or self.param = params - even in inherited classes.
I rebased and pushed the fix.

[boring-cyborg]

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