Refactor: Derive consumer behaviour from queue class (#772)

Derive consumer behaviour from queue class, remove
consumer_type parameter

The queue class prefix (flow, request, response, notify) now
fully determines consumer behaviour in both RabbitMQ and Pulsar
backends.  Added 'notify' class for ephemeral broadcast (config
push notifications).  Response and notify classes always create
per-subscriber auto-delete queues, eliminating orphaned queues
that accumulated on service restarts.

Change init-trustgraph to set up the 'notify' namespace in
Pulsar instead of old hangover 'state'.

Fixes 'stuck backlog' on RabbitMQ config notification queue.

trustgraph-cli/trustgraph/cli/init_trustgraph.py

@@ -138,10 +138,10 @@ def init_pulsar(pulsar_admin_url, tenant):
         }
     })
 
-    ensure_namespace(pulsar_admin_url, tenant, "state", {
+    ensure_namespace(pulsar_admin_url, tenant, "notify", {
         "retention_policies": {
-            "retentionSizeInMB": 10,
-            "retentionTimeInMinutes": -1,
+            "retentionSizeInMB": -1,
+            "retentionTimeInMinutes": 3,
             "subscriptionExpirationTimeMinutes": 5,
         }
     })

trustgraph-cli/trustgraph/cli/monitor_prompts.py

@@ -123,7 +123,6 @@ async def monitor(flow, queue_type, max_lines, max_width, **config):
         topic=request_queue,
         subscription="prompt-monitor-req",
         schema=None,
-        consumer_type='shared',
         initial_position='latest',
     )
 
@@ -131,7 +130,6 @@ async def monitor(flow, queue_type, max_lines, max_width, **config):
         topic=response_queue,
         subscription="prompt-monitor-resp",
         schema=None,
-        consumer_type='shared',
         initial_position='latest',
     )