fix: release beds/lockers in batchCheckOut

The batchCheckOut method was not releasing assigned beds and lockers
after checkout, leaving them orphaned as 'occupied'. Added the same
release pattern used in checkOut() — using runner.manager.update()
since batchCheckOut operates inside a QueryRunner transaction.

apps/server/src/entities/class.entity.ts

@@ -64,6 +64,9 @@ export class Class {
   @Column({ name: 'notes', type: 'text', nullable: true })
   notes: string;
 
+
+  @Column({ name: 'is_archived', default: false })
+  isArchived: boolean;
   @CreateDateColumn({ name: 'created_at' })
   createdAt: Date;
 

apps/server/src/entities/user.entity.ts

@@ -35,6 +35,9 @@ export class User {
   @Column({ name: 'last_login_at', type: 'datetime', nullable: true })
   lastLoginAt: Date;
 
+  @Column({ name: 'is_archived', default: false })
+  isArchived: boolean;
+
   @CreateDateColumn({ name: 'created_at' })
   createdAt: Date;