feat(resource-detector-aws): add support for cloud.resource_id to AWS ECS detector

[mmanciop]

Which problem is this PR solving?

Add support for cloud.resource_id in the AWS ECS detector.

Short description of the changes

Implement setting the ContainerARN as value to cloud.resource_id in the AWS ECS detector as discussed in this issue in semantic-conventions.

Since the OpenTelemetry SDK missing the enum entry for cloud.resource_id (to be fixed in this PR), a temporary enum is added to the package.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.47%. Comparing base (dfb2dff) to head (9ec3c9f).
Report is 105 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1936      +/-   ##
==========================================
- Coverage   90.97%   90.47%   -0.51%     
==========================================
  Files         146      149       +3     
  Lines        7492     7592     +100     
  Branches     1502     1591      +89     
==========================================
+ Hits         6816     6869      +53     
- Misses        676      723      +47     

Files	Coverage Δ
...ource-detector-aws/src/detectors/AwsEcsDetector.ts	96.90% <100.00%> (+0.03%)	⬆️
...or-aws/src/detectors/SemanticResourceAttributes.ts	100.00% <100.00%> (ø)

... and 35 files with indirect coverage changes

[mmanciop]

@JamieDanielson may I interest you in a review? This logic has been already implemented in most other SDKs that support ECS detectors (.NET, Go, Java, PHP), and has been in review purgatory for... well... forever :-)

(Pinging you because I saw you reviewing another PR in this package, namely #2047)

[maryliag]

I still don't see the changes @pichlermarc commented here, so until then this PR looks like a good solution