Add Datadog Synthetic tests workflow

[onejjm001-cell]

This workflow triggers Datadog Synthetic tests on push and pull request events to the master branch, using specified API and application keys.

Change Summary

What does this PR change?

Related Issue/Ticket:

Testing & Verification

How was this tested?

• Unit tests
• Integration tests
• Manual testing (describe steps)
• Verified on staging

Risk Assessment

Risk Level:

• Low - Minor changes, no operational impact
• Medium - Moderate changes, limited impact, standard rollback available
• High - Significant changes, potential operational impact, complex rollback

Risks & Impact

---

Note

Low Risk
CI-only addition; merge/push builds can fail if secrets are missing or tagged synthetics fail, and the workflow relies on a third-party Datadog action.

Overview
Adds a new GitHub Actions workflow that runs Datadog Synthetic checks on every push and pull request targeting master.

The job checks out the repo and invokes the pinned DataDog/synthetics-ci-github-action (v1.4.0), using repository secrets DD_API_KEY and DD_APP_KEY, and only runs synthetics matching tag:e2e-tests. This wires e2e synthetics into CI without changing application code.

^{Reviewed by Cursor Bugbot for commit 0f79437. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 0f79437. Configure here.}

[cursor]

Fork PRs fail without secrets

Medium Severity

The pull_request job always calls the Datadog action with DD_API_KEY and DD_APP_KEY. GitHub withholds repository secrets from fork pull requests, so those runs get empty keys and the action fails. External contributor PRs then show a failing check.

Additional Locations (1)

• .github/workflows/datadog-synthetics.yml#L33-L35

 

^{Reviewed by Cursor Bugbot for commit 0f79437. Configure here.}