Refactor entry reservation handling by generalizing ticket reservations

- Renamed `desfile_entry_reservations` to `entry_reservations` and `desfile_reservation_batches` to `reservation_batches`.
- Updated models, services, and requests to use the new `EntryReservation` model from the `Ticket` domain instead of the deleted `Desfile` model.
- Introduced a new `EntryReservationPaymentType` enum to manage payment types.
- Modified database migrations to ensure data integrity during the transition.
- Updated tests to reflect changes in the database schema and model relationships.
- Ensured that existing functionality remains intact while improving code organization and clarity.

tests/Feature/Ticket/AdminAppTicketEventScopeTest.php

@@ -72,7 +72,7 @@ class AdminAppTicketEventScopeTest extends TestCase
             $table->unsignedBigInteger('purchase_item_id');
             $table->decimal('amount', 12, 2);
         });
-        Schema::create('desfile_entry_reservations', function (Blueprint $table): void {
+        Schema::create('entry_reservations', function (Blueprint $table): void {
             $table->id();
             $table->unsignedBigInteger('ticket_id');
             $table->softDeletes();