fix: weekly view was not clickable when meeting duration is 25 minutes (#25344)

[sudoKrishna]

What does this PR do?

This PR fixes an issue where the Weekly Calendar View becomes unclickable when using non-standard meeting durations such as 25 minutes. The issue occurred because the grid layout relied on 60 / eventDuration, which produces fractional values (example: 60 / 25 = 2.4), leading to:

Misaligned calendar cells

Unresponsive click regions

Overlay events failing to apply correctly

This update replaces fractional grid sizing with a consistent normalized 5-minute interval layout, making the calendar fully interactive and visually stable regardless of the selected duration.

Fixes

Fixes #25344

Fixes CAL-25344

Visual Demo
Before (Broken behavior):

Screen.Recording.2025-11-24.125544.mp4

After (Fixed behavior):

Video.Project.mp4

How should this be tested?

Open the weekly view calendar.

Set the event duration to 25 minutes (or any duration not divisible by 60).

Click any available time slot.

Expected behavior:

✔️ Time slot becomes selectable

✔️ Hover state and selection logic behave normally

✔️ Overlay-busy events still render correctly

✔️ UI behaves consistently with 15m, 30m, and 60m slots

No environment variables or configuration changes required.

Checklist

Code follows existing styling patterns

Added comments for non-trivial logic

No new console warnings introduced

[vercel]

@sudoKrishna is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title " Fix: Weekly view was not clickable when meeting duration is 25 minutes   #25344". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[cubic-dev-ai]

No issues found across 2 files

[Udit-takkar]

@sudoKrishna Please remove un related changes in packages/prisma/.env and .gitignore

[Udit-takkar]

Still the same problem #25358 (review).

You need to make sure you don't push changes that are not needed for the fix. you don't have to delete .gitignore file but keep it same as before and same of prisma/.env