[LogsDB] [Stack 8.19.20-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - sysmetric) in oracle.sysmetric

- Stack version: 8.19.20-SNAPSHOT
- LogsDB: enabled
- Package: oracle
- Failing test: system test: (elastic-agent logs - sysmetric)
- DataStream: sysmetric
- Owners:
- @elastic/obs-infraobs-integrations

Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs3826271668: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-a88f1aea-3f81-4553-9be2-36daff5fcddf (HEALTHY->DEGRADED): Error fetching data for metricset sql.query: cannot open connection: testing connection: user=\"sys\" standalone params={authMode:2 connectionClass: connectionClassLength:0 purity:0 newPassword: newPasswordLength:0 appContext: numAppContext:0 externalAuth:0 externalHandle: pool: tag: tagLength:0 matchAnyTag:0 outTag: outTagLength:0 outTagFound:0 shardingKeyColumns: numShardingKeyColumns:0 superShardingKeyColumns: numSuperShardingKeyColumns:0 outNewSession:0}: ORA-12541: TNS:no listener"
```

First build failed: https://buildkite.com/elastic/integrations/builds/47076

Latest 5 failed builds:
- https://buildkite.com/elastic/integrations/builds/48320
- https://buildkite.com/elastic/integrations/builds/48399
- https://buildkite.com/elastic/integrations/builds/48456
- https://buildkite.com/elastic/integrations/builds/48531
- https://buildkite.com/elastic/integrations/builds/48613

Start with the latest failed Buildkite build and inspect the oracle package's system test for the sysmetric data stream. Trace the elastic-agent logs failure showing ORA-12541 and compare it with the first failed build to identify whether the test or its Oracle service setup changed. Done means the test passes reliably in the LogsDB-enabled 8.19.20-SNAPSHOT workflow.

Written by the indexing model from the issue text.