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

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

Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs2219179566: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-21755cab-2b4e-45ea-81c6-2c056860e4cb (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/49028

Latest failed builds:
- https://buildkite.com/elastic/integrations/builds/49092
- https://buildkite.com/elastic/integrations/builds/49170
- https://buildkite.com/elastic/integrations/builds/49243
- https://buildkite.com/elastic/integrations/builds/49335

Start with the failing `elastic-agent logs - performance` system test for the Oracle `performance` data stream and compare the listed Buildkite failures. Investigate why the SQL metricset cannot reach the Oracle listener; done means the test completes without the ORA-12541 connection error.

Written by the indexing model from the issue text.