chore(aws-sdk): bump aws-sdk version to align with previous releases

[blumamir]

This is another attempt to fix #1153
I previously fixed it in #1247, but I forgot to update .release-please-manifest.json, so the fix had no effect.
Hopefully, this one will work

[codecov]

Codecov Report

Merging #1302 (f693f70) into main (28ad01e) will increase coverage by 0.54%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1302      +/-   ##
==========================================
+ Coverage   96.08%   96.62%   +0.54%     
==========================================
  Files          14       25      +11     
  Lines         893     1454     +561     
  Branches      191      309     +118     
==========================================
+ Hits          858     1405     +547     
- Misses         35       49      +14     

Impacted Files	Coverage Δ
...entation-aws-sdk/src/services/MessageAttributes.ts	91.89% <0.00%> (ø)
...ntation-aws-sdk/src/services/ServicesExtensions.ts	100.00% <0.00%> (ø)
...entelemetry-instrumentation-aws-sdk/src/aws-sdk.ts	97.45% <0.00%> (ø)
...y-instrumentation-aws-sdk/src/services/dynamodb.ts	100.00% <0.00%> (ø)
...try-instrumentation-aws-sdk/src/services/lambda.ts	97.77% <0.00%> (ø)
...emetry-instrumentation-aws-sdk/src/services/sqs.ts	100.00% <0.00%> (ø)
...opentelemetry-instrumentation-aws-sdk/src/enums.ts	100.00% <0.00%> (ø)
...tapackages/auto-instrumentations-node/src/utils.ts	98.21% <0.00%> (ø)
...emetry-instrumentation-aws-sdk/src/services/sns.ts	93.75% <0.00%> (ø)
...etry-instrumentation-aws-sdk/src/services/index.ts	100.00% <0.00%> (ø)
... and 1 more

[Flarna]

not sure here but isn't it needed to use fix or feat commit type to ensure that release please actually creates a new release?

[blumamir]

not sure here but isn't it needed to use fix or feat commit type to ensure that release please actually creates a new release?

🤔good point, I don't really know. @dyladan - can you help?

[blumamir]

not sure here but isn't it needed to use fix or feat commit type to ensure that release please actually creates a new release?

Anyway, this change is not urgent, so it can be merged and just join the next release when it happens.
Since it's not really a fix or a feature, I think it does not deserve a bullet in the CHANGELOG.