VaultStaticSecret merge secrets from multiple path to one kubernetes secret

**Is your feature request related to a problem? Please describe.**
We have one shared secret path for all services. And per service also has its specific secret path.

Could we use one VaultStaticSecret to merge multiple path into one Kubernetes secret?
**As below at` path`, instead one path, it accepts a list of paths**

```
apiVersion: secrets.hashicorp.com/v1beta1
kind: VaultStaticSecret
metadata:
namespace: app
name: app1-static-secret
spec:
namespace: application
mount: secret
type: kv-v2
path:
- app1/shared-secrets
- app1/specific-secrets
refreshAfter: 60s
destination:
create: true
name: app-secret
```

Start by reading the VaultStaticSecret specification and reconciliation flow, focusing on how the path and destination fields are handled. Check the existing Kubernetes Secret behavior and related tests, then define how multiple Vault paths are combined and how conflicting keys are resolved. Done means one VaultStaticSecret can merge the requested paths into the named Kubernetes Secret with documented, tested behavior.

Written by the indexing model from the issue text.