[cmd/opampsupervisor] Report bad remote config to OpAMP server

[evan-bradley]

Component(s)

No response

Is your feature request related to a problem? Please describe.

Currently, the Supervisor only tries to compose the effective configuration for the Collector before reporting that remote configuration has been applied. We should instead check to make sure that the Collector successfully starts or fails to start before reporting that it has been successfully applied or failed respectively.

Describe the solution you'd like

Wait to receive a healthcheck or crash from the Collector before reporting the final remote configuration status to the server. The Supervisor can still report that it is applying the remote configuration as it composes the effective configuration and signals the Collector to load the new configuration.

It should be clarified whether changing telemetry/other connection settings should also trigger the Supervisor to report that a remote config has been applied.

I'm considering all Collector pipelines starting to be a successfully applied configuration even if the configuration may have bugs while handling telemetry records. We could consider using a configurable waiting period or number of healthchecks to be required before declaring the configuration as applied.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[srikanthccv]

I can pick this up.