Add #ddev-silent-no-warn to config.coder.yaml to suppress startup warnings

[rfay]

The Issue

config.coder.yaml and ~/.ddev/traefik/custom-global-config/coder-routes.yaml are generated by ddev coder-setup and managed by coder-ddev, but do not carry either the #ddev-generated or #ddev-silent-no-warn marker. As a result, DDEV's custom config detection treats it as a user-created custom file and emits a warning on every ddev start/ddev restart:

Custom configuration detected in project 'myproject':
  • Config: /home/coder/myproject/.ddev/config.coder.yaml

Background

DDEV v1.25 introduced #ddev-silent-no-warn (PR #7660) specifically for this case: files that are intentionally custom (or managed by external tooling) but should not produce startup noise. Adding this comment anywhere in config.coder.yaml tells DDEV to skip it in startup warnings while still making it visible via ddev utility check-custom-config (marked with (#ddev-silent-no-warn)).

Proposed Fix

Add #ddev-silent-no-warn to the header comment block in the config.coder.yaml template and also the generated coder-routes.yaml file

# Coder-specific DDEV hooks (auto-generated by ddev coder-setup, do not edit)
# #ddev-silent-no-warn

This is the correct solution — using #ddev-generated would be wrong because config.coder.yaml is not managed by DDEV's own file generation system, and a mismatched #ddev-generated marker would itself be flagged as suspicious by DDEV (see ddev/ddev#8218).