captureAWSClient adding significant latency to lambda invocations

When testing the durations of our lambda invocations we are noticing a difference of close to a second in duration time when the lambda clients are wrapped with `captureAWSClient`. We are using version 3.3.1 of `aws-xray-sdk-core`

Start by reproducing Lambda invocation timings with and without captureAWSClient using aws-xray-sdk-core version 3.3.1. Compare the wrapped and unwrapped paths to isolate the source of the nearly one-second difference. Done means the overhead is explained and a fix or documented limitation is established.

Written by the indexing model from the issue text.