[all] Use of component.UseLocalHostAsDefaultHost

[mx-psi]

Component(s)

No response

Describe the issue you're reporting

Once open-telemetry/opentelemetry-collector/pull/8622 gets merged and we add a similar package to contrib, we need to use the feature gate in the following components:

• Use localhost feature gate on extension/healthcheck #30818
• Use localhost feature gate on internal/aws/proxy #30986
• Use localhost feature gate on extension/awsproxy #30984
• Use localhost feature gate on extension/jaegerremotesampling #30982
• Use localhost feature gate on receiver/jaegerreceiver #30979
• Use localhost feature gate on receiver/skywalkingreceiver #30977
• Use localhost feature gate on receiver/sapmreceiver #30843
• Use localhost feature gate on receiver/signalfxreceiver #30844
• Use localhost feature gate on receiver/influxdbreceiver #30911
• Use localhost feature gate on receiver/awsxrayreceiver #30823
• Use localhost feature gate on receiver/zookeeperreceiver #30867
• Use localhost feature gate on receiver/opencensusreceiver #30816
• Use localhost feature gate on receiver/lokireceiver #30819
• Use localhost feature gate on receiver/zipkinreceiver #30821
• Use localhost feature gate on receiver/awsfirehosereceiver #30825
• Use localhost feature gate on receiver/splunkhecreceiver #30845
• Use localhost feature gate on receiver/jmxreceiver
• Use localhost feature gate on processor/remotetapprocessor

For each component we should:

1. Change the default configuration to use the helper function
2. Update documentation to say that this feature gate will change the default behavior
3. Update any examples to use 0.0.0.0 if needed

See #30820 for an example

This is on hold for now, will remove the label and add more detailed instructions when we can move forward with this

[atoulme]

For processor/remotetapprocessor, given that it's alpha, I will elect to make a direct breaking change. I will post the PR here for review and make sure folks can 👍 / 👎 as needed

[mx-psi]

No longer on hold. I marked JMX receiver as done since the endpoint is for an internal OTLP exporter, not for a receiver.

[atoulme]

Change of plans for remotetapprocessor, it will use the feature gate after all: #30905