feat: add compatibility-date

[shyim]

No description provided.

[Copilot]

Pull request overview

Adds documentation for a new compatibility_date setting in Shopware CLI configuration files, explaining how it can be used to gate behavior changes.

Changes:

• Adds compatibility_date to the .shopware-project.yml example and documents its purpose/behavior.
• Adds compatibility_date to the .shopware-extension.yml example and documents its purpose/behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
products/cli/project-commands/build.md	Documents compatibility_date for project builds and adds it to the sample .shopware-project.yml.
products/cli/extension-commands/configuration.md	Documents compatibility_date for extension configuration and adds it to the sample .shopware-extension.yml.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Section heading uses the raw config key (compatibility_date) while the rest of this document’s headings use title-style phrases. Consider renaming the heading to something like “Compatibility date” and refer to the exact key in the body text/code block to keep headings consistent and more readable in the TOC.

Suggested change

	## compatibility_date
	## Compatibility date

[Copilot]

The heading compatibility_date is inconsistent with other headings in this doc (e.g., “Environment variables”), which are human-readable/title-style. Consider changing the heading to “Compatibility date” while still showing the exact YAML key in the example to improve readability/TOC consistency.

Suggested change

	## compatibility_date
	## Compatibility date