Bump traefik from v3.7.5 to v3.7.6 in /compose/production/traefik

[dependabot]

Bumps traefik from v3.7.5 to v3.7.6.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[claude]

Review

This is a minimal, single-line Dependabot patch bump (traefik:v3.7.5 → v3.7.6) in compose/production/traefik/Dockerfile. No application code, GraphQL, permissioning, or frontend logic is touched, so the usual review dimensions don't really apply here:

• Code quality: N/A — pinned base image tag bump only, consistent with existing Dockerfile conventions.
• Bugs: None introduced. This is a patch-level release (v3.7.5 → v3.7.6), so no breaking changes are expected per Traefik's semver policy.
• Performance: No impact.
• Security: Positive — keeping the Traefik base image current on patch releases is good hygiene for the edge proxy; patch releases often include security fixes upstream. Worth a quick check of the Traefik v3.7.6 release notes to confirm no CVE-relevant regressions, but nothing here suggests concern.
• Test coverage: N/A for a base image tag bump; existing CI/build pipeline will validate the image builds correctly.

No changes requested — safe to merge once CI passes.