### 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)

#
#
from __future__ import annotations
import hvac
from hvac.api.auth_methods import Kubernetes
from hvac.exceptions import InvalidPath, VaultError
from requests import Response
from airflow.compat.functools import cached_property
from airflow.utils.log.logging_mixin import LoggingMixin
DEFAULT_KUBERNETES_JWT_PATH = "/var/run/secrets/kubernetes.io/serviceaccount/token"
DEFAULT_KV_ENGINE_VERSION = 2
VALID_KV_VERSIONS: list[int] = [1, 2]
VALID_AUTH_TYPES: list[str] = [
    "approle",
    "aws_iam",
    "azure",
    "github",
    "gcp",
    "kubernetes",
    "ldap",
    "radius",
    "token",
    "userpass",
]
class _VaultClient(LoggingMixin):