[Fleet] APM Integration with Per Integration Output does not allow selecting policy with non-Elasticsearch output

[BenB196]

Kibana version: 8.16.2

Elasticsearch version: 8.16.2

Server OS version: Container

Browser version: N/A

Browser OS version: N/A

Original install method (e.g. download page, yum, from source, etc.): ECK

Describe the bug:

When attempting to install the APM integration on a non-Elasticsearch default output agent policy, but setting a custom output that is Elasticsearch, the policy is still greyed out.

Steps to reproduce:

1. Create a non-Elasticsearch output (ex: Logstash)
2. Create an Elasticsearch output
3. Create an Elastic Agent policy and set the default output to what was created in step 1.
4. Attempt to add an APM Integration to the policy created in step 4, but under Advanced of the APM integration, set the Output to the Elasticsearch output created in step 2.
5. Attempt to assign the APM integration to the policy created in step 3
6. Observe that the policy is greyed out and can't be selected

Expected behavior:

I would expect to be able to select the policy, as I have explicitly defined a valid (per integration) output to the APM integration

Screenshots (if relevant):

Output configuration:

Policy Configuration with non-Elasticsearch default output:

Attempt to add APM Integration with integration specific Elasticsearch output

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

This can currently be worked around by switching the default output, but becomes bad UX when the majority of integrations use Logstash and require each out to be manually set, rather than just being able to manually set the per integration for APM integration.