refactor: Remove trpc/server dependency from @calcom/atoms

[tomerqodo]

Benchmark PR from qodo-benchmark#716

[augmentcode]

🤖 Augment PR Summary

Summary: Refactors the platform @calcom/atoms package to avoid direct dependencies on @calcom/trpc/server types.

Changes:

• Replaced tRPC server type/schema imports in atoms hooks with locally-defined schedule/slot types.
• Added atoms-local schedule types (and a basic input validator) and expanded booker types to include available-slot response shapes.
• Updated tests to import slot types from @calcom/atoms/booker/types instead of tRPC.
• Tightened lint/tsconfig constraints to prevent atoms from importing from @calcom/trpc.

Technical Note: This keeps atoms decoupled from server-only tRPC modules while preserving type coverage for the REST endpoints it calls.

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

[augmentcode]

Review completed. 4 suggestions posted.

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

[augmentcode]

Slot.userIds is typed as string[], but the previous tRPC Slot type and other slot-related code paths use numeric user IDs (number[]). This mismatch can cause downstream type errors or incorrect assumptions when consuming onTimeslotsLoaded data.

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

[augmentcode]

SlotInfo.fromUser.id is typed as string, but the shared availability types (IFromUser) use a numeric id: number. If the API returns numbers here, this will mis-type the response for any consumers that rely on fromUser.id.

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

[augmentcode]

availability.days is typed as string[], but the atoms /schedules/all endpoint delegates to the tRPC availability list handler which returns numeric weekday indices (number[]) from Prisma. This mismatch can break consumers like getScheduleListItemData/ScheduleListItem that expect number[].

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

[augmentcode]

validateCreateScheduleInput only validates name and then casts the entire object to CreateScheduleInput, so invalid schedule/eventTypeId shapes can still pass. This function name suggests full validation, so callers may get a false sense of safety.

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