chore: Cache timezones by calcom version

[keithwillcode]

After reviewing our bandwidth usage, I see we are not caching timezones aggressively enough. Considering they rarely change and we can use a similar mechanism to what we did with i18n where we cache by calcom version, decided to implement for this as well.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
ai	⬜️ Ignored (Inspect)	Visit Preview		Jun 24, 2024 10:12pm
cal	⬜️ Ignored (Inspect)	Visit Preview		Jun 24, 2024 10:12pm
calcom-web-canary	⬜️ Ignored (Inspect)	Visit Preview		Jun 24, 2024 10:12pm

[graphite-app]

Graphite Automations

"Add foundation team as reviewer" took an action on this PR • (06/24/24)

1 reviewer was added to this PR based on Keith Williams's automation.

[github-actions]

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Eleven Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/apps/[slug]/[...pages]	593.33 KB	821.03 KB	234.58% (🟡 +0.20%)
/auth/saml-idp	12.22 KB	239.92 KB	68.55% (🟢 -20.80%)
/event-types	566.36 KB	794.06 KB	226.87% (🟡 +0.29%)
/settings/admin/lockedSMS/UsersTable	79.88 KB	307.58 KB	87.88% (🟢 -0.17%)
/settings/admin/lockedSMS/lockedSMSView	119.37 KB	347.06 KB	99.16% (🟢 -0.20%)
/settings/admin/oAuth/oAuthView	95.43 KB	323.13 KB	92.32% (🟢 -0.19%)
/settings/organizations/[id]/about	159.59 KB	387.29 KB	110.65% (🟡 +0.46%)
/settings/organizations/[id]/add-teams	159.58 KB	387.28 KB	110.65% (🟡 +0.45%)
/settings/organizations/new	159.6 KB	387.29 KB	110.66% (🟡 +0.45%)
/settings/platform/new	120.65 KB	348.34 KB	99.53% (🟡 +0.50%)
/video/[uid]	290.75 KB	518.44 KB	148.13% (🟢 -0.31%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

[zomars]