fix: define VERT service in file provider instead of referencing Docker provider

Fixed "the service 'vert-web-secure@docker' does not exist" error by defining
the service directly in the vert-sablier.yaml file provider configuration.

Previously, the router was defined in the file provider but tried to reference
a service from the Docker provider (@docker suffix), which caused a mismatch.
Now both the router and service are defined in the same file provider, while
still using Docker-based middlewares (auth, compression).

Changes:
- Added services.vert-web-secure with loadBalancer pointing to vert_app:80
- Changed router service reference from "vert-web-secure@docker" to "vert-web-secure"

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

proxy/dynamic/vert-sablier.yaml

@@ -10,10 +10,16 @@ http:
             displayName: VERT File Converter
             theme: ghost
 
+  services:
+    vert-web-secure:
+      loadBalancer:
+        servers:
+          - url: "http://vert_app:80"
+
   routers:
     vert-web-secure:
       rule: "Host(`vert.pivoine.art`)"
-      service: vert-web-secure@docker
+      service: vert-web-secure
       entryPoints:
         - web-secure
       middlewares: