deploy: image now under m/ namespace on mgit.msbls.de

m granted mAi admin on m/mCables, but Gitea's container registry is
user-namespace-scoped (not repo-collab-scoped) so the push had to go
through m's own credentials for this one administrative move:

    docker login mgit.msbls.de -u m -p <m's token>
    docker push mgit.msbls.de/m/mcables:latest

Image digest sha256:76624f17… is identical to the one previously living
at mgit.msbls.de/mai/mcables:latest — same build, just retagged.

Drops the workaround comment from the compose file. The mai/mcables
package will be deleted via API after the deploy verifies.

docker-compose.yml

@@ -4,12 +4,7 @@
 
 services:
   mcables:
-    # Pushed under the mAi namespace because the mAi token doesn't have
-    # write permission to the m/* namespace on mgit.msbls.de today. If m
-    # later grants mAi collaborator access on m/mCables, retag to
-    # mgit.msbls.de/m/mcables:latest and align with the other mDock
-    # services (msports-garmin, mgreen-journal, …).
-    image: mgit.msbls.de/mai/mcables:latest
+    image: mgit.msbls.de/m/mcables:latest
     container_name: mcables
     restart: unless-stopped
     ports: