fix(platform): apply production hardening from audit plan

Close billing, tenancy, migration, build, and CI/CD gaps identified in the
audit: wallet/gateway guards, full-UUID namespaces, idempotent migrations with
base schema, stateful service stability, safer Dockerfiles/git builds, and
platform chart hardening (Redis auth, RollingUpdate, backups, Swagger off).

Co-authored-by: Cursor <cursoragent@cursor.com>

backend/src/kubernetes/kubernetes.service.spec.ts

@@ -15,7 +15,7 @@ describe('buildHelmValues logic', () => {
     return {
       app: {
         name: app.name,
-        namespace: `user-${app.userId.split('-')[0]}`,
+        namespace: `user-${app.userId.replace(/-/g, '')}`,
         runtime: app.runtime,
         image: imageUri,
         port: app.port,
@@ -72,7 +72,7 @@ describe('buildHelmValues logic', () => {
 
   it('should set correct namespace from userId', () => {
     const values = buildHelmValues(baseApp, 'registry/my-app:123');
-    expect(values.app.namespace).toBe('user-abc123');
+    expect(values.app.namespace).toBe('user-abc123def456');
   });
 
   it('should disable database when type is NONE', () => {