Fix AWS instrumentation destination.service.resource handling

[JonasKunz]

What does this PR do?

Closes #2946, closes #2849 .

While implementing these fixes I enhanced the test cases of all AWS instrumentations to check for the correct service.target.* and destination.service.resource fields.
These tests unconvered that at least to my reading we currently deviate from the spec for DynamoDB:
Currently service.target.name is always null for DynamoDB, according to the spec it should be the AWS region instead.

I changed the DynamoDB instrumentation to follow the spec with this PR aswell. If my reading is wrong here, we should remove this change from the PR.

Checklist

• This is a bugfix
  • I have updated CHANGELOG.asciidoc
  • I have added tests that would fail without this fix

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-17T15:39:22.990+0000

• Duration: 64 min 13 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3398
Skipped	42
Total	3440

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark tests.

• run jdk compatibility tests : Run the JDK Compatibility tests.

• run integration tests : Run the Agent Integration tests.

• run end-to-end tests : Run the APM-ITs.

• run windows tests : Build & tests on windows.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[github-actions]

/test