fix(tracer): properly return DynamoDB.DocumentClient

[dreamorosi]

Description of your changes

This PR aims at fixing the bug identified in #524.

How to verify this change

Check GitHub actions execution results, the unit tests now include test cases to assert on the type of client being returned.

Related issues, RFCs

#524

PR status

Is this ready for review?: YES
Is it a breaking change?: NO

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• The PR title follows the conventional commit semantics

Breaking change checklist

N/A

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[dreamorosi]

Attaching an archive with a packed version of this branch (npm pack) and the same code you find in the linked issue (#524 ) so that you can verify the change easily. Just download, unzip, and run npm i in the folder to run the code (set up a DynamoDB table using the provided createTable.json).

fix_test.zip

[flochaz]

Could you add get or put calls in the e2e as well ?

[dreamorosi]

Here at this link you can find a successful e2e test execution with the new changes.

[ijemmy]

LGTM. Thanks for also updating the e2e tests.

[ijemmy]

Thanks for the detailed investigation!

[ijemmy]

@dreamorosi question just for myself.

Why do we cast to unknown first and as T in the 2nd step?

[dreamorosi]

You are right, it's a leftover from a previous experiment and it's not needed since T is already a generic. Fixed in latest commit.