fix(queues): avoid ':' in BullMQ job ids (fixes #32)

[webparadoxer]

Summary

Fixes #32 — sendNotification always fails with Custom Id cannot contain :.

BullMQ rejects custom jobIds containing : (it's the reserved Redis key separator). The notification queue was building ids with colons:

• `fanout:${data.notificationId}` in `addFanoutNotificationJob`
• `notification:${notificationId}:device:${deviceId}` and `notification:${notificationId}:channel:${channelId}:${to}` in `getSendNotificationJobId`

For channel/Web Push jobs, `to` is also an endpoint URL (`https://fcm.googleapis.com/...\`) — so colons leak in from there too.

Fix

• Replace `:` with `-` as the separator in all custom job ids.
• Sanitize colons out of the channel `to` segment before composing the id.
• Update existing tests and add one that verifies a URL-shaped `to` never leaks a `:` into the id.

Test plan

• `pnpm test` passes locally for the updated `notification-queue.test.ts`
• Manual: `createApp` → `configureWebPush` → `registerDevice` (web) → `sendNotification { channelType: PUSH }` — previously failed with `Custom Id cannot contain :`, now succeeds and delivers.

Determinism (same id for same `(notificationId, deviceId)` / `(notificationId, channelId, to)` pair) is preserved, so BullMQ's dedup behavior is unchanged.

[webparadoxer]

any updates?

[productdevbook]

Please excuse the delay. I’ve been busy publishing several npm package.