revert: roll back VP9/AV1 codec test (Issue #11)

Real testing (Safari + Firefox, fresh rejoins) confirmed VP9 selection
always falls back to VP8 - our fork's buildPublishOptions() forces
simulcast:true unconditionally, which breaks LiveKit's SVC negotiation
path that vp9/av1 require. This is the same failure mode originally
suspected in the 2026-07-28 incident; the "LiveKit handles this
automatically" assumption from doc research did not hold up in
practice. Reverting to the known-safe VP8/H.264/H.265 SFU allow-list
and widget image. Root cause documented in Issue #11 for a future,
scoped fix (conditional simulcast vs. scalabilityMode per codec).

apps/production/element-server-suite.yaml

@@ -74,26 +74,6 @@ spec:
           cpu: 50m
         limits:
           memory: 128Mi
-      sfu:
-        # Issue #11 test (2026-07-29): opt-in VP9/AV1 support. LiveKit's built-in
-        # default enabled_codecs list is [VP8, H264, H265, rtx, PCMU, PCMA, opus, red]
-        # (confirmed live via SFU negotiation logs) - VP9/AV1 appended, nothing removed,
-        # so the existing default path is unaffected either way.
-        additional:
-          0-codecs:
-            config: |
-              room:
-                enabled_codecs:
-                  - mime: video/VP8
-                  - mime: video/H264
-                  - mime: video/H265
-                  - mime: video/rtx
-                  - mime: audio/PCMU
-                  - mime: audio/PCMA
-                  - mime: audio/opus
-                  - mime: audio/red
-                  - mime: video/VP9
-                  - mime: video/AV1
 
     # Element Web
     elementWeb:
@@ -101,7 +81,7 @@ spec:
       image:
         registry: rohana.axion1337.de
         repository: sorb/threadnet-web
-        tag: v0.2.7-elementcall-vp9av1test
+        tag: v0.2.6-elementcall-realcodecs
       ingress:
         host: axion1337.chat