Custom ResourceDetector discovery should fail gracefully when entry point not found

[cruisehall]

Is your feature request related to a problem?

N/A

Describe the solution you'd like

When the SDK cannot find an entry point indicated by the OTEL_EXPERIMENTAL_RESOURCE_DETECTORS env var it should handle the exception gracefully and continue processing other entry points (or proceed with initialization).

Describe alternatives you've considered

No response

Additional Context

As a member of a platform team that provides common observability utilities, I would like to bake in default value for this environment variable at the infrastructure layer for all of my internal users (e.g. using a common dockerfile) such that they can automatically use a custom resource detector provided by my team.

The current behavior, in which the SDK initialization fails if an entrypoiny is not found, creates an implicit dependency between infrastructure and application code.

Would you like to implement a fix?

Yes