chore: Integrate confirmation booking audit

[tomerqodo]

Benchmark PR from qodo-benchmark#714

[augmentcode]

🤖 Augment PR Summary

Summary: This PR integrates booking confirmation/rejection flows with the booking-audit system by attaching a concrete actor and actionSource to actions.

Changes:

• Pass actionSource/actor into confirmation/rejection from API v2, the webapp (tRPC), and magic-link endpoints.
• Emit booking-audit events for accepted/rejected bookings (including bulk/recurring series) via BookingEventHandlerService.
• Add getAppActor helper and use it for payment-webhook-triggered confirmations to attribute actions to an app.
• Extend booking-audit producer interfaces and Tasker producer implementation to support bulk rejected audits.
• Update booking-audit action source typing and add MAGIC_LINK as a persisted source (Prisma enum + migration).
• Expand route and handler tests, and add an integration test covering accepted audit log persistence/formatting.

Technical Notes: Introduces ValidActionSource (client-facing sources excluding UNKNOWN) and app actors that prefer credentialId but fall back to appSlug when unavailable.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

acceptedBookings is populated with oldStatus: BookingStatus.ACCEPTED for the single-booking path, which makes the audit/event payload show ACCEPTED -> ACCEPTED instead of the real status transition.

_{🤖 Was this useful? React with 👍 or 👎}

[augmentcode]

In the recurring rejection path, rejectedBookings is built from updatedRecurringBookings after the update, so oldStatus will be REJECTED (and the audit status change becomes REJECTED -> REJECTED).

_{🤖 Was this useful? React with 👍 or 👎}