[extension/beatsauthextension] Use the component status API to report errors

[cmacknz]

If the beatsauthextension encounters a fatal error it returns an error, which eventually causes the collector to exit.

For example, invalid or non-existent certificates will be detected we unpacking the configuration for use via elastic-agent-libs

opentelemetry-collector-components/extension/beatsauthextension/authenticator.go

Line 58 in f0b0051

err = parsedCfg.Unpack(&beatAuthConfig)

Instead of causing the collector to exit, the extension should (perhaps optionally) report it's status as failed via the component status API https://pkg.go.dev/go.opentelemetry.io/collector/component/componentstatus

Ultimately the goal of this is that failures can be associated back to the relevant Elastic Agent output as is the case for Beats based ingest today: elastic/elastic-agent#9771

[cmacknz]

#796