chore(docs): Tracer docs

[dreamorosi]

Description of your changes

Created documentation for Tracer according to current implementation in #107.

How to verify this change

Checkout branch locally & run npm run docs-runLocalDocker to run docs locally.

Related issues, RFCs

#153

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
• I have made corresponding changes to the documentation
• 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
• Any dependent changes have been merged and published in downstream module
• 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]

Converted to draft until I've worked also on JSDocs for the module, depends on:

• feat: generate api docs #277
• feat: add tracer #107

[saragerion]

Looking good!
Minor: in the code snippets you are not highlighting the important lines of code.
Example: line 6 in the first code snippet of this section:
http://localhost:8000/core/tracer/#patching-aws-sdk-clients

[dreamorosi]

Recap of changes:

• Created JSDocs for all public & private methods of the Tracer Class
• Created documentation (MKDocs) for the module

Note: There are some placeholder/TODOs in both annotations & docs for the middleware which I'll complement in the appropriate PR.