Add ECS and Logs attributes based on Metadata v4 endpoint

[mmanciop]

Changes

Implement aws.ecs and aws.log resource attributes with data from the ECS Metadata endpoint v4.

• Appropriate CHANGELOG.md updated for non-trivial changes

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mmanciop / name: Michele Mancioppi (32b8b57, 7be379e, 395da02, dabb78a, 7c7c9c3, 212e90a, 49ac4d3)

[utpilla]

@mmanciop Please sign the CLA.

[mmanciop]

I am actually not 100% sure yet of the patchset wrt the implementation of the IResourceDetector interface. I am going to try it out on a test app.

Update: It seems to me we need to get rid of the local IResourceDetector if we want this to work with OpenTelemetry SDK 1.3.0+.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mmanciop / name: Michele Mancioppi (32b8b57, 7be379e, 395da02, dabb78a, 7c7c9c3, 212e90a, 49ac4d3, f06b8f5, 50d8ead, 912d21d, 4fdd4bd, eb7a43f, 3c5403f)

[Kielek]

@srprash, @lupengamzn could you please check?

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.

[Kielek]

@srprash?

[github-actions]

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

[srprash]

@srprash, @lupengamzn could you please check?

Would you review? And also comment on the breaking change/major version bump as well?

I agree that this must go out as a major version bump.

Just a reminder, in case of major bump, the whole package should be renamed. At least .Contrib infix has to be removed.

Yup. We can do that to be inline with the rest of the packages in the repo. I wish we can do the same for the OpenTelemetry.Contrib.Instrumentation.AWS package as well while bumping its major version.

If renaming the package is being considered, could we please replace XRay with AWS in the name?

I have no issues in dropping XRay and renaming the package to be OpenTelemetry.Contrib.Extensions.AWS. We had it with XRay because initially the package contained only the id-generator and the propagator very specific to AWS XRay.

[Kielek]

@mmanciop, finally we have an approval from the package owner.
Could you please solve the conflicts? Then we should be able to make final review and merge.

[mmanciop]

@Kielek @srprash I solved the conflicts and did some cleanup, but I am assuming that version bumping, extension renaming and the rest mentioned in #875 (comment) will be performed by the package owners, right?

[Kielek]

For sure as a separate PR.

[mmanciop]

@mmanciop, finally we have an approval from the package owner. Could you please solve the conflicts? Then we should be able to make final review and merge.

Now that I found out why PublicApiAnalyzers did not run in my setup (#1071), I dearly hope this commit is it :-)