Create internal/metadataproviders module

[mx-psi]

Description:

Move the metadata providers for different environments used in the resource detection processor to a new internal module.
The goal is to reduce duplication in the usage of these metadata clients among different components (namely, we want to use some of these in the Datadog exporter).

In the future, it would also be nice to handle things like retries and caching in a common way for all components, to avoid e.g. one component being able to query the AWS EC2 endpoint while another times out; but this is out of scope on this particular PR, which tries to only make minimal changes on the code moved to the new module.

Link to tracking Issue: Relates to #1379 and #10424

Testing: Original unit tests are kept

[mx-psi]

@Aneurysm9 @pmm-sumo @dashpole would you mind having a look at this? Although the diff is large, the changes are mostly either renames or go.mod/go.sum updates, so it shouldn't take too long to review

[pmm-sumo]

I'm curious what's @bogdandrutu take on how it fits the larger vision on component relationship within the collector.

One alternative approach would be be moving the detectors into an extension. It would have pros and cons but then would be easier to refer by other components (e.g. for components outside of the contrib)

[mx-psi]

I'm curious what's @bogdandrutu take on how it fits the larger vision on component relationship within the collector.

One alternative approach would be be moving the detectors into an extension. It would have pros and cons but then would be easier to refer by other components (e.g. for components outside of the contrib)

@pmm-sumo I think that is a fair question (since components that use an internal module won't be able to be moved outside of this repository for now), but I don't think we need to solve this on this PR because it's not a problem specific to this new internal module: the problem existed before and we are not making it any worse by doing this (other than having a couple more components depend on internal modules, but if we are worried about that we should ban internal modules entirely I guess).

In my mind the solution eventually would be to move this new metadataproviders module into a module inside pkg/ instead, but for that we would have to carefully think about the public API and think about where do we want this to live.

[TylerHelmuth]

LGTM

[mx-psi]

Marking as ready to merge since we have two approvals, one from a CODEOWNER

[codeboten]

@mx-psi please resolve the conflicts and we can merge this

[mx-psi]

@codeboten Thanks for the ping, should be ready to merge now!