fix: ensure correct run-context for instrumented aws-sdk client usage

[trentm]

This fixes aws-sdk (S3, SQS, SNS) instrumentation to ensure the
automatically created AWS spans do not spill into user code. This also
ensures that any captured APM error for a failed AWS command is a child
of the AWS span.

Refs: #2430

Checklist

• Implement code
• Add tests
• Add CHANGELOG.asciidoc entry

[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-01T21:36:34.727+0000

• Duration: 19 min 13 sec

• Commit: 61706e5

Test stats 🧪

Test	Results
Failed	0
Passed	22
Skipped	0
Total	22

🤖 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!)

[astorm]

👍 Approving -- also, re:

This also
ensures that any captured APM error for a failed AWS command is a child
of the AWS span.

Just to say this a bit more loudly, with the callback bound correct bound, the _setOutcomeFromErrorCapture code is no longer needed captureError will now set this value on the correct span.