[TEST] Non-reorg conflict on a top-level file (not auto-fixable)

[jhgilbert]

Test PR for exercising the astro reorg tooling. Creates a conflict on a top-level file that the reorg doesn't move, so it isn't a reorg conflict and should go straight to manual review.

Do not merge.

[datadog-prod-us1-6]

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/documentation | build_preview     

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 12f6b01 | Docs | Datadog PR Page | Give us feedback!}

[jhgilbert]

This PR has merge conflicts from a recent repo reorg that could not be resolved automatically.

If you feel comfortable resolving the conflicts yourself:

1. Resolve the conflicts. For a full list of repo files and folders and their updated location, see the configuration file for the reorg script.
2. When your PR is ready for merge, remove the WORK IN PROGRESS label.
3. Wait for the standard docs team approval before merging. Optionally, you can check the 'ready for merge' checkbox in the PR description if you would like the docs team to merge it for you.

If you prefer that we resolve your conflicts, add the label astro-reorg-help-requested to your PR. This will add it to our support queue, and we will reach out to you as soon as possible.

This is an automated comment, but if you have a question, you can mention me in this PR (external contributors) or reach out in #docs-repo-reorg-support on Slack (internal contributors).