feat: add tracking to docs site using reodev and google tag manager

[arora-saurabh448]

Summary

What changed and why?

Test Plan

How was this tested?

Checklist

• Tests added/updated
• Documentation updated (if needed)
• CHANGELOG updated (if user-facing)

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review.

[sentry]

Bug: The custom_dir is configured to be inside the docs_dir, which violates MkDocs constraints and will cause the documentation build to fail.
_{Severity: CRITICAL}

Suggested Fix

Move the overrides directory to docs/overrides (making it a sibling to the documentation source files) and update the custom_dir setting in mkdocs.yml to overrides.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: docs/mkdocs.yml#L11

Potential issue: The `custom_dir` is set to `docs/overrides` in `mkdocs.yml`. Since the
`docs_dir` is not explicitly set, it defaults to `docs`, resolving to `docs/docs/`. This
makes the `custom_dir` path (`docs/docs/overrides/`) a subdirectory of the `docs_dir`.
MkDocs explicitly validates that the `custom_dir` must not be a child of the `docs_dir`.
This misconfiguration will cause a validation error during the build phase, preventing
the documentation from being generated.

_{Did we get this right? 👍 / 👎 to inform future reviews.}