Add support for vault-enterprise container image in log pipeline (DataDog#22565)

* Add support for vault-enterprise container image in log pipeline

Update the Vault log pipeline filter to accept logs from both vault
and vault-enterprise container images. This enables automatic log
processing for Vault Enterprise deployments in Kubernetes where the
sidecar container image name differs from the standard Vault image.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* Add vault-enterprise to installation-sources

* Fix query format

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: dkirov-dd

vault/assets/logs/vault.yaml

@@ -2,6 +2,9 @@
 id: vault
 metric_id: vault
 backend_only: false
+installation_sources:
+  - vault
+  - vault-enterprise
 facets:
   - groups:
       - Web Access
@@ -128,16 +131,16 @@ pipeline:
   name: Vault
   enabled: true
   filter:
-    query: source:vault
+    query: source:(vault OR vault-enterprise)
   processors:
     - type: grok-parser
       name: Parsing Vault Server logs
       enabled: true
       source: message
       samples:
         - 2019-11-04T17:48:44.226-0800 [WARN]  no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set
-        - '2019-11-04T17:48:58.967-0800 [DEBUG] core: starting cluster listeners'
-        - '2019-11-04T17:48:58.967-0800 [INFO]  core.cluster-listener: starting listener: listener_address=0.0.0.0:8201'
+        - "2019-11-04T17:48:58.967-0800 [DEBUG] core: starting cluster listeners"
+        - "2019-11-04T17:48:58.967-0800 [INFO]  core.cluster-listener: starting listener: listener_address=0.0.0.0:8201"
       grok:
         supportRules: |
           _date %{date("yyyy-MM-dd'T'HH:mm:ss.SSSZ"):timestamp}