feat(azure): add Queue Storage to Cloud Explorer

[xujiantop-crypto]

Summary

Add Azure Queue Storage to the Cloud Explorer separately from Azure Service Bus. The adapter uses Floci-AZ's Storage Queue REST API through the shared Azure runtime client. The existing explorer provides queue listing, creation, inspection, and deletion; message operations are outside this PR.

Queue listing follows continuation markers until completion, including beyond 100 pages, while rejecting repeated markers. Search includes every page. When Azure returns an idempotent 204 for an existing queue, the console reports a 409 conflict instead of claiming it created a new queue.

Closes #94. The issue's older CloudProxyService fallback instructions are covered by the current adapter registry.

Type of change

• Bug fix (fix:)
• New feature / service UI (feat:)
• Breaking change (feat!: or fix!:)
• Docs / chore

Area

• Frontend (packages/frontend)
• API / Cloud Proxy (packages/api)
• Cloud Explorer adapter / schema
• Build / CI / Docker

Verification

• Integrated main c3e0aef and resolved the dependency conflict, keeping main's versions alongside the Queue adapter's saxes dependency. Both lockfiles were actually regenerated with pnpm 9.2.0 and Bun 1.4.2 in an isolated copy of the tested tree; the generated files matched that tree exactly. This also aligns the Bun lock with main's SNS 3.1141.0 manifest. Queue implementation and regression tests are unchanged by this synchronization.
• The final local tree e4414648 passed sequential frozen pnpm/Bun installations, 1,504 API tests, 73 frontend tests, lint, both packages' type checks and production build with Node 24.19.0, Bun 1.4.2 and pnpm 9.2.0. The complete generated service matrix matches the README.
• API regression coverage includes valid listings beyond 100 pages, repeated markers, malformed XML, duplicate-create 409 and the generic routes. The 101-page case uses protocol fixtures; it is not a real 101-page Floci-AZ runtime test.
• This same tree passed the actual local Hono API, CloudProxy, adapter and Floci-AZ HTTP chain: empty list, create, duplicate-create 409, filtered list, inspection with message count, invalid-name 400, delete, post-delete 404 and empty list. SNS and CloudWatch schemas remained available. The temporary queue was deleted and both owned processes were stopped.
• The local walkthrough used Java 25 and the existing Floci-AZ 0.13.0 binary from the earlier fba2ec4 build. No fresh Floci-AZ build, live Azure/AWS behavior, or separate browser walkthrough is claimed. GitHub checks for the synchronization commit must be assessed on that exact head; previous b0b9e67 checks do not establish its result. Human review remains pending.

Checklist

• pnpm lint, pnpm type-check, API/frontend tests, and pnpm build pass locally
• New or updated adapter, catalog, and route tests added
• No fake resource data added
• Commit messages and PR title follow Conventional Commits
• No layout or look-and-feel changes; this service uses existing Cloud Explorer views
• No more than 2 open, non-draft pull requests in this repository

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Adds Azure Queue Storage support to the cloud explorer.

The PR appears safe to merge; no outstanding finding or actionable new issue was identified.

Summary

Adds Azure Queue Storage as a separate Cloud Explorer service for listing, creating, inspecting, and deleting queues. It also adds pagination and duplicate-create handling, tests, documentation, and dependency updates.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  UI[Cloud Explorer] --> Routes[Generic cloud routes]
  Routes --> Proxy[Cloud proxy]
  Proxy --> Registry[Adapter registry]
  Registry --> Queue[Azure Queue adapter]
  Queue --> Client[Shared Azure runtime client]
  Client --> Runtime[Queue Storage REST API]

Loading

_{Reviews (7) · Last reviewed commit: "fix(azure): resolve Queue Storage depend..."}

[fredpena]

Thank you for the Queue Storage work, @xujiantop-crypto, and for the careful pagination and duplicate-create handling.

(blocking) Main moved with the dependency bump (#283), so the PR now conflicts in packages/api/package.json and both lockfiles. Would you merge main, keep its versions plus saxes, and regenerate bun.lock and pnpm-lock.yaml? It resolved mechanically for me.

No other blockers from my side.

[xujiantop-crypto]

Merged main c3e0aef, kept its dependency versions alongside saxes, and regenerated both lockfiles with pnpm 9.2.0 and Bun 1.4.2. The regenerated files match the tested merge tree.

Frozen installs, all 1,504 API and 73 frontend tests, lint, type checks and build passed locally. I also reran the actual local Queue API/Floci-AZ walkthrough, including duplicate-create 409 and deletion, and cleaned up the temporary queue and processes. This uses the existing Floci-AZ 0.13.0 binary; it does not verify live Azure. GitHub checks for the new head are tracked separately.