feat: Implement console session management with tenant and profile handling

- Add ConsoleSessionStore for managing console session state including tenants, profile, and token information.
- Create OperatorContextService to manage operator context for orchestrator actions.
- Implement OperatorMetadataInterceptor to enrich HTTP requests with operator context metadata.
- Develop ConsoleProfileComponent to display user profile and session details, including tenant information and access tokens.
- Add corresponding HTML and SCSS for ConsoleProfileComponent to enhance UI presentation.
- Write unit tests for ConsoleProfileComponent to ensure correct rendering and functionality.

etc/signals.yaml.sample

@@ -0,0 +1,28 @@
+# Signals service configuration template.
+# Copy to ../etc/signals.yaml (relative to the Signals content root)
+# and adjust values to fit your environment.
+
+schemaVersion: 1
+
+Signals:
+  Authority:
+    Enabled: true
+    Issuer: "https://authority.stella-ops.local"
+    AllowAnonymousFallback: false
+    Audiences:
+      - "api://signals"
+    RequiredTenants:
+      - "tenant-default"
+    RequiredScopes:
+      - "signals:read"
+      - "signals:write"
+      - "signals:admin"
+    BypassNetworks:
+      - "127.0.0.1/32"
+      - "::1/128"
+  Mongo:
+    ConnectionString: "mongodb://localhost:27017/signals"
+    Database: "signals"
+    CallgraphsCollection: "callgraphs"
+  Storage:
+    RootPath: "../data/signals-artifacts"