Migrate consumers to URL-scoped /providers/:pp/... endpoints

[AquiGorka]

Summary

• Migrate every consumer in this repo to the URL-scoped surface introduced by URL-scope every per-provider endpoint + signed-challenge entity submission provider-platform#107. Affected: e2e/dashboard.ts (channels/mempool/operations/treasury/metrics/audit-export), e2e/main.ts, e2e/pos-instant/main.ts, e2e/governance/uc2-approve-reject.ts, lifecycle/{main,testnet-verify,ci-test}.ts, testnet/main.ts, setup-pp.{sh,ts}, lib/client/bundle.ts. Comments and section headers updated to name the new URLs.
• Add lib/client/register-entity.ts — a shared SEP-43/SEP-53 signed-challenge KYC submission helper, replacing six in-place registerEntity copies across e2e/, lifecycle/, testnet/ that hit the bare-deleted POST /api/v1/entities. Living under lib/client/ so every docker-compose test-runner that already copies /lib-src/client/ reaches it.
• Rewrite send-loop.ts:forceExpireBundles to write status='EXPIRED' + back-dated TTL directly to the provider-platform PostgreSQL via postgres. Replaces the bare-deleted HTTP admin endpoint POST /api/v1/dashboard/bundles/expire; the back-dated TTL lets the platform's mempool TTL-check sweep purge the in-memory slot via the same path it uses for natural TTL expiry. There's a short race window: when the executor wins the race to settle, the verifier later transitions the bundle to COMPLETED; when our UPDATE + back-dated TTL win, the bundle stays EXPIRED. In both cases the bundle reaches a terminal status, which is what INJECT_EXPIRE exists to produce. (A race-free guarantee would require in-process mempool access we deliberately don't expose over HTTP.)

Test-infra fix

• docker-compose.pos-instant.yml's test-runner entrypoint only copied top-level lib/*.ts into the container — it skipped the lib/client/ subdirectory the other suites already copy. After register-entity.ts moved into lib/client/, the suite errored with Module not found "file:///app/lib/client/register-entity.ts". Adding cp -r /lib-src/client lib/ aligns pos-instant with the other suites' mount shape; the import path becomes ./lib/client/register-entity.ts to match the container-flattened layout the other pos-instant imports use (./moonlight-pay-lib/…, ./e2e/…).

URL changes (consumer side)

e2e/governance/lifecycle/testnet/setup-pp now hit:
  POST   /providers/:pp/entity/bundles                 (user-mode submit)
  GET    /providers/:pp/entity/bundles/:id             (user-mode poll)
  POST   /providers/:pp/council/join                   (operator)
  GET    /providers/:pp/council/membership             (operator)
  POST   /providers/:pp/council/membership             (operator sync)
  GET    /providers/:pp/{channels,mempool,operations,
         treasury,metrics,audit-export}                (operator dashboard)

entity registration uses lib/client/register-entity.ts:
  POST   /providers/:pp/entities/challenge             (issue nonce)
  POST   /providers/:pp/entities                       (signed submit)

Companion PRs

• URL-scope every per-provider endpoint + signed-challenge entity submission provider-platform#107
• Migrate all per-PP API calls to URL-scoped paths + KYC submission route provider-console#37
• URL-scope bundle submission to /providers/:pp/entity/bundles pay-platform#36

Test plan

• deno fmt --check, deno lint (23 pre-existing warnings, none new)
• test.sh e2e, otel, governance, lifecycle, pos-instant, invite-gate — all green against the companion branches
• testnet/run-local.sh payment + lifecycle — 23 OTEL checks each, green
• send-loop.ts EXPIRE=true — 12-country cycle, force-expire writes EXPIRED to DB (force-expired 1 of 1 bundle(s) via DB (TTL back-dated…)); at-rest DB shows EXPIRED for the one bundle whose UPDATE landed before settlement and COMPLETED for the others (race outcome, both terminal — see Summary)