fix(ci): isolate package Telegram QA harness (#120193)

* fix(qa): isolate package Telegram harness

Keep private QA source, dependencies, taxonomy, and SDK dist in the trusted harness while the installed candidate owns its CLI, Gateway runtime, and persisted mock auth. Preserve the documented package RTT canary after taxonomy selection.

Co-authored-by: Dallin Romney <dallinromney@gmail.com>

Co-authored-by: Vincent Koc <vincentkoc@ieee.org>

* fix(qa): export private QA harness SDK entries

Canonicalize the QA-only plugin SDK entries shared by the private build and package Telegram harness manifest so qa-runtime and qa-lab resolve from trusted dist.

* fix(qa): expose private runtime to package harness

* fix(qa): surface Telegram observer conflicts

* fix(qa): accept separate preview and final messages

* test(qa): exercise Telegram poll delay contract

---------

Co-authored-by: Peter Steinberger <steipete@gmail.com>
Co-authored-by: Vincent Koc <vincentkoc@ieee.org>

qa/scenarios/channels/channel-canary.yaml

@@ -21,6 +21,9 @@ scenario:
     - extensions/qa-lab/src/suite.ts
   execution:
     kind: flow
+    channels:
+      - qa-channel
+      - telegram
     summary: Run the shared channel canary through QA Channel, Crabline, or a live adapter.
     transportPolicy:
       requireGroupMention: true

qa/scenarios/channels/channel-message-flows.yaml

@@ -29,6 +29,7 @@ scenario:
     - extensions/telegram/src/draft-stream.ts
   execution:
     kind: flow
+    retryCount: 0
     channels:
       - qa-channel
       - telegram