docs(cli): add Local Proxy page (run multiple shops in parallel)

[Tomasz Turkowski (tturkowski)]

What

Adds a new CLI reference page documenting shopware-cli project proxy — running several local Shopware shops at once, each on its own stable HTTPS hostname (e.g. https://my-shop.shopware.local) behind one shared reverse proxy, instead of fighting over fixed host ports.

Relates to the shopware-cli feature in shopware/shopware-cli#1208. Issue shopware/shopware-cli#1094

Page

products/tools/cli/project-commands/local-proxy.md (nav position 2, right after Development Environment):

• Intro — the port-conflict problem and what the proxy solves
• How it works — a Mermaid sequence diagram (browser → CoreDNS → Traefik → shop) plus a short explanation (CoreDNS resolver, shared Traefik, local CA)
• One-time setup — proxy setup (the single sudo moment), --domain
• Two workflows — new project (create --local-domain → dev) and existing project (proxy up / down)
• Command reference — setup / up / down / status / list / verify / teardown, with a proxy list example
• Choosing the hostname, troubleshooting (proxy verify), requirements (Docker; macOS/Linux; Windows via WSL2)

Linking

• Cross-linked from dev-environment.md ("Further reading").
• Added Traefik, WSL2, CoreDNS to .wordlist.txt (sorted) for spellcheck.

Notes

The underlying shopware-cli PR is still in review. Feedback on wording/placement welcome.

[shopware-dev-docs-connector]

Developer Docs healthcheck

Status: Completed with success.
Repository: shopware/docs
Commit: 670c471
Preview: https://developer-documentation-9n1ht98mb-shopware-frontends.vercel.app
Workflow run: #4832

[somethings (lasomethingsomething)]

Heya Micha Hobert (@Isengo1989) and Bojan Rajh (@bojanrajh), this feature is going live in the new CLI release we plan to ship on Monday, Aug. 17. If you have time to take a look, we're greatly appreciate it.

[github-actions]

📢 Developer Announcement Recommendation

Recommendation: ❌ No Announcement Recommended

No developer announcement signals were detected.

This PR does not appear to introduce developer-facing changes that require a community announcement.