Fix/telegram parity stt fiat shared prisma

[devfoma]

Four issues, one commit each on this branch.

#402: Telegram now requires confirmation before any deposit/withdraw intent executes
and supports alert create/list/delete via the shared alert pipeline. Rules created
through Telegram use delivery channel WEBHOOK because the delivery-channel enum has
no Telegram option and there is no outbound Telegram transport yet.

#400: Adds Deepgram as a secondary speech-to-text backend. If the primary STT
provider is unavailable, transcription falls back to Deepgram; unsupported-audio
errors short-circuit at the primary instead. Behavior is config-controlled.

#399: Adds Transak as a second live fiat on/off-ramp provider alongside MoonPay,
with webhook signature verification, status normalization, and quote/order plumbing
registered into the shared fiat registry.

#392: The compliance case and travel-rule modules now use the shared Prisma client
singleton instead of instantiating their own. A few other modules still construct
their own Prisma clients; they were left untouched as out of scope and can be
migrated in a follow-up.

closes #392

closes #399

closes #400

closes #402

[drips-wave]

@devfoma Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits