containers: add guide for managing DatadogPodAutoscaler resources with Terraform

[kennonkwok]

What does this PR do? What is the motivation?

Adding a guide on managing the DatadogPodAutoscaler resources using Terraform. This has been a frequent topic in conversations with customers.

Merge instructions

No special instructions.

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

[github-actions]

📝 Documentation Team Review Required

This pull request requires approval from the @DataDog/documentation team before it can be merged.

Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes.

[github-actions]

Preview links (active after the build_preview check completes)

New or renamed files

• https://docs-staging.datadoghq.com/kennon/manage-datadogpodautoscaler-with-terraform/containers/guide/manage-datdadogpodautoscaler-with-terraform

Modified Files

• https://docs-staging.datadoghq.com/kennon/manage-datadogpodautoscaler-with-terraform/containers/guide/

[drichards-87]

Created DOCS-11868 for Docs Team review.

[joepeeples]

Thanks for preparing this guide, @kennonkwok! I added some editorial suggestions throughout, and there are a few larger-scale changes that I think would help:

• Streamline the heading structure so it's easier to follow the stages and their sub-steps.
• Refactor code examples to use the code block shortcode, which includes the filename (so we wouldn't need to put filenames in headings)
• Refactor the Additional Resources section into a Further Reading shortcode section

Those changes are hard to convey with GitHub line-edit comments, so I can pull down your branch and add them in separate commits.