Fix unexpected keyword argument 'secret_path' in secrets.kv.v2

[tungbq]

Closes: #37619
Fix unexpected keyword argument 'secret_path' in secrets.kv.v2
Called self.client.secrets.kv.v2.create_or_update_secret() function with path argument instead
Document: https://hvac.readthedocs.io/en/stable/usage/secrets_engines/kv_v2.html#create-update-secret

---

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

[hussein-awala]

It seems no one uses this method in the hook, the bug has been around for years with no reported issues.

[dirrao]

LGTM

[Blizzke]

It seems no one uses this method in the hook, the bug has been around for years with no reported issues.

I was planning on using it, otherwise I wouldn't have encountered the bug 😉
But I mean, I didn't expect to find that method there since the secrets backends don't support (as far as I know) the creation of new secrets, that has to be handled externally. So if the decision is made to remove it, I don't think anyone would miss it (except perhaps the unit tests?)