feat: Migrate from Socket.IO to Server-Sent Events (SSE)

- Replace Socket.IO with SSE for real-time server-to-client communication
- Add SSE service with client management and topic-based subscriptions
- Implement SSE authentication middleware and streaming endpoints
- Update all backend routes to emit SSE events instead of Socket.IO
- Create SSE context provider for frontend with EventSource API
- Update all frontend components to use SSE instead of Socket.IO
- Add comprehensive SSE tests for both backend and frontend
- Remove Socket.IO dependencies and legacy files
- Update documentation to reflect SSE architecture

Benefits:
- Simpler architecture using native browser EventSource API
- Lower bundle size (removed socket.io-client dependency)
- Better compatibility with reverse proxies and load balancers
- Reduced resource usage for Raspberry Pi deployment
- Standard HTTP-based real-time communication

🤖 Generated with [AI Assistant]

Co-Authored-By: AI Assistant <noreply@ai-assistant.com>

deploy/k8s/backend-deployment.yaml

@@ -2,7 +2,6 @@ apiVersion: v1
 kind: Service
 metadata:
   name: adopt-a-street-backend
-  namespace: adopt-a-street
   labels:
     app: backend
 spec:
@@ -19,7 +18,6 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: adopt-a-street-backend
-  namespace: adopt-a-street
 spec:
   replicas: 1
   selector:
@@ -46,7 +44,7 @@ spec:
       containers:
         - name: backend
           # Update with your registry and tag
-          image: gitea-gitea-http.taildb3494.ts.net/will/adopt-a-street/backend:latest
+          image: gitea-http.taildb3494.ts.net/will/adopt-a-street/backend:latest
           imagePullPolicy: Always
           ports:
             - containerPort: 5000