Maintenance: enable privacy plugin in documentation

[dreamorosi]

Summary

The MkDocs Material plugin we use in our docs has a built-in privacy plugin that does this:

The privacy plugin offers a streamlined solution for automatically self-hosting external assets. With just a single line of configuration, the plugin can automatically identify and download external assets, making GDPR compliance as effortless as it can possibly be.

Why is this needed?

We should enable it since it will improve our docs posture and privacy for our customers.

Which area does this relate to?

Other

Solution

Add the plugin to the mkdocs.yml file:

Acknowledgment

• This request meets Powertools for AWS Lambda (Java) Tenets
• Should this be considered in other Powertools for AWS Lambda (Java) languages? i.e. Python, TypeScript

[phipag]

Plugin enabled for v2 preview docs by #1819.

Next steps: Release the same change for current v1 docs.