docs: replace the all docker-compose.yml with compose.yaml

[JamBalaya56562]

Why:

According to official manuals,

The default path for a Compose file is compose.yaml (preferred) or compose.yml that is placed in the working directory.
Compose also supports docker-compose.yaml and docker-compose.yml for backwards compatibility of earlier versions.
If both files exist, Compose prefers the canonical compose.yaml.

So compose.yaml is preferred to docker-compose.yml.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Update documentation to replace references to docker-compose.yml with compose.yaml for consistency across content.

Documentation:

• Replace occurrences of docker-compose.yml with compose.yaml in the style guide
• Update codespaces additional container config documentation to reference compose.yaml instead of docker-compose.yml

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
contributing/style-guide-and-content-model/style-guide.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14
codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/setting-up-your-dotnet-project-for-codespaces.md	fpt ghec	fpt ghec	from reusable
codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/setting-up-your-java-project-for-codespaces.md	fpt ghec	fpt ghec	from reusable
codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/setting-up-your-nodejs-project-for-codespaces.md	fpt ghec	fpt ghec	from reusable
codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/setting-up-your-php-project-for-codespaces.md	fpt ghec	fpt ghec	from reusable
codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/setting-up-your-python-project-for-codespaces.md	fpt ghec	fpt ghec	from reusable

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@JamBalaya56562 Thanks for opening a PR! I suspect this change is correct, but I'm going to check to make sure there's not a reason we're still using docker-compose.yml.

[Sharra-writes]

@JamBalaya56562 Got confirmation this is a good change, so I'll get this added to the merge queue shortly!

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡