fix: run context handling for aws-sdk DynamoDB instrumentation

[trentm]

This also adds a couple aws-sdk-related tests to the TAV=aws-sdk tests.

Refs: #2430

Checklist

• Implement code
• Add tests
• Add CHANGELOG.asciidoc entry
• Commit message follows commit guidelines

[apmmachine]

💚 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: 2021-12-07T23:33:04.394+0000

• Duration: 20 min 9 sec

• Commit: 97d317b

Test stats 🧪

Test	Results
Failed	0
Passed	235018
Skipped	0
Total	235018

🤖 GitHub comments

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

• /test : Re-trigger the build.

• run module tests for <modules> : Run TAV tests for one or more modules, where <modules> can be either a comma separated list of modules (e.g. memcached,redis) or the string literal ALL to test all modules

• run benchmark tests : Run the benchmark test only.

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

[trentm]

@elasticmachine run elasticsearch-ci/docs skiplinkcheck

[astorm]

+1 approved -- looks like a pretty now-standard context swap.

[astorm]

+1 here -- it'd be nice if our linter/CI caught these though (not for this PR, just something to keep in mind for the future)

[trentm]

Yah, agreed. I think we can further configure our standard usage with eslint rules? https://eslint.org/docs/rules/strict

[astorm]

+1 for getting these tests into the tav runner while we're in here.