Feature request: interpolate ${VAR} in Docker Compose labels, and let a label-defined middleware stay off the generated router

[PhilippMolitor]

Use case
I run several deployments of one Compose file (production, staging, previews) on the same Traefik. I want a referer allowlist on an image service: a second router on the service's domain that answers 403 when Referer is another site. Each deployment needs its own host and app origin in the rule, and unique router and middleware names:

labels:
  - 'traefik.http.routers.hotlink-${SERVICE_NAME_IMAGOR}.rule=Host(`${SERVICE_FQDN_IMAGOR}`) && HeaderRegexp(`Referer`, `.+`) && !HeaderRegexp(`Referer`, `^${SERVICE_URL_APP}/`)'
  - 'traefik.http.routers.hotlink-${SERVICE_NAME_IMAGOR}.middlewares=deny-${SERVICE_NAME_IMAGOR}'
  - 'traefik.http.middlewares.deny-${SERVICE_NAME_IMAGOR}.ipallowlist.sourcerange=127.0.0.1/32'

What happens now

1. With "Escape special characters in labels" on, ${SERVICE_NAME_*}, ${SERVICE_FQDN_*} and ${SERVICE_URL_*} stay literal text in the container labels, so the rule never matches.
2. Every traefik.http.middlewares.<name>.* label is added to the generated router (bootstrap/helpers/docker.php, the $middlewares_from_labels block). A middleware meant only for my own router, here a deny-all ipallowlist, ends up on the main router and blocks all traffic.

Ask

1. Fill in Coolify's SERVICE_* variables (and other env variables) in labels before escaping $, or document how to use them in labels.
2. Add a way to keep a label-defined middleware off the generated routers, for example a coolify.traefik.exclude-middlewares=<name> label. Another option is to attach only the middlewares named in coolify.traefik.middlewares.