feat: workspace-based multi-tenancy, replacing user as tenancy axis (#840)

Introduces `workspace` as the isolation boundary for config, flows,
library, and knowledge data. Removes `user` as a schema-level field
throughout the code, API specs, and tests; workspace provides the
same separation more cleanly at the trusted flow.workspace layer
rather than through client-supplied message fields.

Design
------
- IAM tech spec (docs/tech-specs/iam.md) documents current state,
  proposed auth/access model, and migration direction.
- Data ownership model (docs/tech-specs/data-ownership-model.md)
  captures the workspace/collection/flow hierarchy.

Schema + messaging
------------------
- Drop `user` field from AgentRequest/Step, GraphRagQuery,
  DocumentRagQuery, Triples/Graph/Document/Row EmbeddingsRequest,
  Sparql/Rows/Structured QueryRequest, ToolServiceRequest.
- Keep collection/workspace routing via flow.workspace at the
  service layer.
- Translators updated to not serialise/deserialise user.

API specs
---------
- OpenAPI schemas and path examples cleaned of user fields.
- Websocket async-api messages updated.
- Removed the unused parameters/User.yaml.

Services + base
---------------
- Librarian, collection manager, knowledge, config: all operations
  scoped by workspace. Config client API takes workspace as first
  positional arg.
- `flow.workspace` set at flow start time by the infrastructure;
  no longer pass-through from clients.
- Tool service drops user-personalisation passthrough.

CLI + SDK
---------
- tg-init-workspace and workspace-aware import/export.
- All tg-* commands drop user args; accept --workspace.
- Python API/SDK (flow, socket_client, async_*, explainability,
  library) drop user kwargs from every method signature.

MCP server
----------
- All tool endpoints drop user parameters; socket_manager no longer
  keyed per user.

Flow service
------------
- Closure-based topic cleanup on flow stop: only delete topics
  whose blueprint template was parameterised AND no remaining
  live flow (across all workspaces) still resolves to that topic.
  Three scopes fall out naturally from template analysis:
    * {id} -> per-flow, deleted on stop
    * {blueprint} -> per-blueprint, kept while any flow of the
      same blueprint exists
    * {workspace} -> per-workspace, kept while any flow in the
      workspace exists
    * literal -> global, never deleted (e.g. tg.request.librarian)
  Fixes a bug where stopping a flow silently destroyed the global
  librarian exchange, wedging all library operations until manual
  restart.

RabbitMQ backend
----------------
- heartbeat=60, blocked_connection_timeout=300. Catches silently
  dead connections (broker restart, orphaned channels, network
  partitions) within ~2 heartbeat windows, so the consumer
  reconnects and re-binds its queue rather than sitting forever
  on a zombie connection.

Tests
-----
- Full test refresh: unit, integration, contract, provenance.
- Dropped user-field assertions and constructor kwargs across
  ~100 test files.
- Renamed user-collection isolation tests to workspace-collection.

tests/unit/test_query/test_triples_neo4j_query.py

@@ -122,7 +122,6 @@ class TestNeo4jQueryProcessor:
         
         # Create query request
         query = TriplesQueryRequest(
-            user='test_user',
             collection='test_collection',
             s=Term(type=IRI, iri="http://example.com/subject"),
             p=Term(type=IRI, iri="http://example.com/predicate"),
@@ -130,7 +129,7 @@ class TestNeo4jQueryProcessor:
             limit=100
         )
         
-        result = await processor.query_triples(query)
+        result = await processor.query_triples('test_user', query)
         
         # Verify both literal and URI queries were executed
         assert mock_driver.execute_query.call_count == 2
@@ -164,7 +163,6 @@ class TestNeo4jQueryProcessor:
         
         # Create query request
         query = TriplesQueryRequest(
-            user='test_user',
             collection='test_collection',
             s=Term(type=IRI, iri="http://example.com/subject"),
             p=Term(type=IRI, iri="http://example.com/predicate"),
@@ -172,7 +170,7 @@ class TestNeo4jQueryProcessor:
             limit=100
         )
         
-        result = await processor.query_triples(query)
+        result = await processor.query_triples('test_user', query)
         
         # Verify both literal and URI queries were executed
         assert mock_driver.execute_query.call_count == 2
@@ -210,7 +208,6 @@ class TestNeo4jQueryProcessor:
         
         # Create query request
         query = TriplesQueryRequest(
-            user='test_user',
             collection='test_collection',
             s=None,
             p=None,
@@ -218,7 +215,7 @@ class TestNeo4jQueryProcessor:
             limit=100
         )
         
-        result = await processor.query_triples(query)
+        result = await processor.query_triples('test_user', query)
         
         # Verify both literal and URI queries were executed
         assert mock_driver.execute_query.call_count == 2
@@ -248,7 +245,6 @@ class TestNeo4jQueryProcessor:
         
         # Create query request
         query = TriplesQueryRequest(
-            user='test_user',
             collection='test_collection',
             s=Term(type=IRI, iri="http://example.com/subject"),
             p=None,
@@ -258,7 +254,7 @@ class TestNeo4jQueryProcessor:
 
         # Should raise the exception
         with pytest.raises(Exception, match="Database connection failed"):
-            await processor.query_triples(query)
+            await processor.query_triples('test_user', query)
 
     def test_add_args_method(self):
         """Test that add_args properly configures argument parser"""