Clarify CLI formatter Docker requirements

[Soner (shyim)]

Summary

• Explain that formatter, validation, and automatic refactoring commands use PHP and Node.js tooling under the hood
• Clarify that Docker is recommended because the image includes those dependencies
• Add context for the /ext and /project container mount paths versus local paths
• Replace local validation examples that used /ext with /path/to/your/extension

Verification

• git diff --check
• Content assertion for expected clarification text
• make spellcheck using Docker

Note: Two unrelated untracked talk files are present locally and were temporarily moved out before running the Docker spellcheck, then restored.

[Copilot]

Pull request overview

This PR clarifies the runtime/dependency expectations for the Shopware CLI formatter by explaining why Docker-based usage is recommended and how container mount paths (/ext, /project) relate to local filesystem paths.

Changes:

• Document that the formatter relies on PHP and Node.js tooling, and that the Docker image bundles these dependencies.
• Explain the Docker mount targets (/ext and /project) used in the formatter examples.
• Add “without Docker” guidance to use local filesystem paths when running shopware-cli directly.

---

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