Add Datadog Synthetic tests workflow

[Namtanmk]

This workflow triggers Datadog Synthetic tests on push and pull request events to the main branch. It requires Datadog API and Application Keys as secrets.

Summary by Sourcery

CI:

• Introduce a Datadog Synthetic tests GitHub Actions workflow that triggers e2e-tagged tests using repository secrets for Datadog API and application keys.

[sourcery-ai]

Reviewer's Guide

Adds a GitHub Actions workflow that runs Datadog Synthetic tests on pushes and pull requests to the main branch using repository secrets for Datadog API and application keys, filtered by a specific test tag.

File-Level Changes

Change	Details	Files
Introduce a GitHub Actions workflow to trigger Datadog Synthetic tests on main-branch pushes and pull requests.	Create a new GitHub Actions workflow configuration with a descriptive name for running Datadog Synthetic tests. Configure workflow triggers for push and pull_request events limited to the main branch. Define a single job that runs on ubuntu-latest and checks out the repository source code. Integrate the DataDog/synthetics-ci-github-action at a pinned commit corresponding to v1.4.0. Pass Datadog API and Application Keys via GitHub secrets to the action inputs. Specify a default Datadog Synthetic test search query using the tag e2e-tests, with inline guidance to adjust the tag as needed. Include inline documentation and links explaining setup of Datadog keys and additional configuration options for the action.	.github/workflows/datadog-synthetics.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider renaming the job from build to something like datadog-synthetics to better reflect its purpose and make the workflow easier to understand at a glance.
• Running this workflow on both push and pull_request events to main may result in duplicate runs for merged PRs; you might want to restrict one of the triggers (e.g., push to main only) depending on your desired behavior.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider renaming the job from `build` to something like `datadog-synthetics` to better reflect its purpose and make the workflow easier to understand at a glance.
- Running this workflow on both `push` and `pull_request` events to `main` may result in duplicate runs for merged PRs; you might want to restrict one of the triggers (e.g., `push` to `main` only) depending on your desired behavior.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}