fix(agent-pod): route /run and /sessions through Kong too

Ingress only covered /console -- agent-console run got a 404 hitting
/run since Kong had no route for it. Same Service, same port, just
more paths on the one Ingress.

k8s/apps/agent-pod/console-ingress.yaml

@@ -1,4 +1,5 @@
-# Exposes agent-hub at api.riotpiao.com/console.
+# Exposes agent-hub at api.riotpiao.com/console (WebSocket) and /run
+# (trigger a new session) -- both are routes on the same hub.js service.
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
@@ -19,3 +20,17 @@ spec:
                 name: agent-hub
                 port:
                   number: 9090
+          - path: /run
+            pathType: Prefix
+            backend:
+              service:
+                name: agent-hub
+                port:
+                  number: 9090
+          - path: /sessions
+            pathType: Prefix
+            backend:
+              service:
+                name: agent-hub
+                port:
+                  number: 9090