add host.id to resource auto-detection

[mwear]

This PR adds host id detection support for non-containerized hosts. The implementation is based on this spec pr: open-telemetry/opentelemetry-specification#3173.

Fixes #3811

Summary

• This PR introduces a hostIDReader interface with platform specific implementations for Darwin, Linux, BSD, Windows and a fallback for unsupported platfoms.
• The platform specific implementations use unprivileged means to lookup the host.id, aka machine id for non-containerized environments. Depending on platform this involves reading files in well known locations, excuting shell commands, or a combination of the two.
• I followed the code organization used for the OS Description Detector, which also has platform specific implementations, however, there is one notable difference. Currently the Go SDK divides platform specific code into darwin, unix, and windows and the associated build tags for those platforms. Host id detection is more granular and requires dividing unix into linux and BSD.

See also

• Spec PR: clarify how to collect host.id for non-containerized systems opentelemetry-specification#3173
• JS Implementation: feat: detect host id for non-cloud environments opentelemetry-js#3575
• Collector PR (using gopsutil): resourcedetectionprocessor: use opentelemetry-go for host id detection opentelemetry-collector-contrib#18740

I realize we will want to see the spec PR merge before getting too serious about this work, but I wanted to get some eyes on the approach and encourage anyone with opinions to provide feedback here and on the spec PR.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@1eab60f). Click here to learn what that means.
The diff coverage is 74.0%.

❗ Current head 6df6880 differs from pull request most recent head 3230472. Consider uploading reports for the commit 3230472 to get more accurate results

Additional details and impacted files

@@          Coverage Diff           @@
##             main   #3812   +/-   ##
======================================
  Coverage        ?   81.5%           
======================================
  Files           ?     170           
  Lines           ?   12765           
  Branches        ?       0           
======================================
  Hits            ?   10415           
  Misses          ?    2131           
  Partials        ?     219           

Impacted Files	Coverage Δ
sdk/resource/host_id.go	73.0% <73.0%> (ø)
sdk/resource/config.go	100.0% <100.0%> (ø)

[pellared]

Shouldn't we add hostIDDetector to WithHost()? We might consider adding WithHostName to offer a resource detector that only sets host.name resource attribute.

[mwear]

Because the rules for detecting HostID are different for containerized vs non-containerized hosts I didn't want to couple the hostIDDetector to WithHost, although I had considered it. My thoughts were that someone who wanted to use WithHost on a cloud provider wouldn't have to worry about detector order when detecting HostID. However, I could see having WithHost that detects HostID and HostName, and separate options WithHostID and WithHostName to collect the attributes individually. Let me know what your preference is.

[pellared]

EDIT: After second thought, I have no strong preference. Maybe we should improve the docs and list all the attributes that given detector (option) should set? This could be addressed in a separate issue as I feel this is a problem not only for this detector/option.

[mwear]

I wanted to check in to see if there is anything that anyone would like to see addressed in this PR?