[service] Include component id/type in start error

[rogercoll]

Description

Wraps the component ID and type into the component's start retuned error. If telemetry::logs::level is < error (e.g fatal), the service error message does not give information about which pipeline component failed:

Current error message:

 $ otelcontribcol --config config.yaml
Error: cannot start pipelines: start function error
2024/12/10 10:07:25 collector server run finished with error: cannot start pipelines: start function error

With these changes:

$ otelcontribcol --config config.yaml
Error: cannot start pipelines: failed to start geoip processor: start function error
2024/12/10 09:58:29 collector server run finished with error: cannot start pipelines: failed to start geoip processor: start function error

Link to tracking issue

#10426

Testing

Documentation

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.77%. Comparing base (461a355) to head (32e5880).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11837   +/-   ##
=======================================
  Coverage   91.77%   91.77%           
=======================================
  Files         462      462           
  Lines       24886    24886           
=======================================
  Hits        22840    22840           
  Misses       1664     1664           
  Partials      382      382           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.