### Description

Support mounting to multiple namespaces with the Hashicorp Vault Secrets Back-end

### Use case/motivation

As a data engineer I wish to utilize secrets stored in multiple mount paths (to support connecting to multiple namespaces)  without having to mount to a higher up namespace.

### Related issues

_No response_

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

"""
        Reads secret metadata (including versions) from the engine. It is only valid for KV version 2.
        :param secret_path: The path of the secret.
        :return: secret metadata. This is a Dict containing metadata for the secret.
                 See https://hvac.readthedocs.io/en/stable/usage/secrets_engines/kv_v2.html for details.
        """
        if self.kv_engine_version == 1:
            raise VaultError("Metadata might only be used with version 2 of the KV engine.")
        try:
            return self.client.secrets.kv.v2.read_secret_metadata(
                path=secret_path, mount_point=self.mount_point
            )
        except InvalidPath:
            self.log.debug("Secret not found %s with mount point %s", secret_path, self.mount_point)
            return None
    def get_secret_including_metadata(