fix(aws-sdk): use custom client_context prop

[smoke]

Which problem is this PR solving?

In every other language the respected property carrying the context is custom e.g.

• https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/9a7f7125ab3f77c47a46be524f29e150536fba6f/instrumentation/aws-sdk/aws-sdk-2.2/library/src/main/java/io/opentelemetry/instrumentation/awssdk/v2_2/internal/LambdaImpl.java#L41

Short description of the changes

• rename Custom to custom property that is used as context carrier for AWS Lambda Client Context

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.64%. Comparing base (6cce92b) to head (dd61438).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2718   +/-   ##
=======================================
  Coverage   89.64%   89.64%           
=======================================
  Files         184      184           
  Lines        9032     9032           
  Branches     1852     1852           
=======================================
  Hits         8097     8097           
  Misses        935      935           

Files with missing lines	Coverage Δ
...try-instrumentation-aws-sdk/src/services/lambda.ts	97.77% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[smoke]

@blumamir @jj22ee @trivikr Sorry to bother, please let me know if you need anything more on this PR.

It is really sad that AWS Documentation is misleading https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html
The documentation is wrong instead of
Custom – Custom values that are set by the client application.
it should be
custom – Custom values that are set by the client application.

I have just filed a feedback form, hopefully to correct it.

[smoke]

@blumamir @jj22ee @trivikr The AWS documentation is now updated https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html

Can you please merge and release this PR?

[jj22ee]

Thanks! You may need to merge with main to get the remaining checks to run.

[jj22ee]

Also @smoke, did injectLambdaPropagationContext never work properly before? If it worked in some capacity, I was wondering if this should be labelled as a breaking change.

[smoke]

Also @smoke, did injectLambdaPropagationContext never work properly before? If it worked in some capacity, I was wondering if this should be labelled as a breaking change.

It never worked, probably.