minio: declare the route contribution it has always needed, scoped from PR #58

files-api.novox.be and files.novox.be worked earlier tonight from route-
adapter-generated files, but minio's module.json on main never actually
carried a route requirement — that capability has been sitting in PR #58
the whole time, bundled with an unrelated network rename and console
redirect URL that need their own calmer review. This is just the two
routes: requires: route, contributes.route.api/.console (ContributesMany,
proven working via mesh-controller #55/#57), and the console port (9001)
actually published and declared in listens.

Found assigning route-proxy for the first time tonight: its own routes
file, generated the identical way route-adapter's always was, had four
hostnames in it instead of six — nothing served files-api/files at all,
which would have been a real, silent outage the moment Traefik stopped.

modules/minio/module.json

@@ -7,6 +7,21 @@
       "scope": "mesh"
     }
   ],
+  "requires": [
+    "route"
+  ],
+  "contributes": {
+    "route": {
+      "api": {
+        "label": "files-api",
+        "port": 9000
+      },
+      "console": {
+        "label": "files",
+        "port": 9001
+      }
+    }
+  },
   "capabilities": [
     "container-runtime"
   ],
@@ -20,6 +35,12 @@
       "protocol": "tcp",
       "from": "mesh",
       "why": "the S3 endpoint"
+    },
+    {
+      "port": 9001,
+      "protocol": "tcp",
+      "from": "mesh",
+      "why": "the admin console"
     }
   ],
   "serves": {
@@ -92,7 +113,8 @@
         "/var/lib/minio/root.env"
       ],
       "ports": [
-        "9000"
+        "9000",
+        "9001"
       ],
       "volumes": [
         "/var/lib/minio-store:/data",