chore: [app-router-migration-4]: apps/categories page

[DmytroHryshyn]

What does this PR do?

Migrates apps/categories, apps/categories/[category] pages.

This PR depends on #12593

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Mandatory Tasks

• Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

[vercel]

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

A member of the Team first needs to authorize it.

[github-actions]

Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link to collect XP and win prizes!

[github-actions]

📦 Next.js Bundle Analysis for @calcom/web

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

One Page Changed Size

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

Page	Size (compressed)	First Load	% of Budget (350 KB)
/bookings/[status]	316.83 KB	480.79 KB	137.37% (🟡 +0.84%)

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.

[hariombalhara]

I don't know the reason but I am seeing a consistent crash on accessing http://app.cal.local:3000/apps/categories with future mode.
https://www.loom.com/share/66d37da1d31940c39691f04d7e695e0a

[DmytroHryshyn]

I don't know the reason but I am seeing a consistent crash on accessing http://app.cal.local:3000/apps/categories with future mode. https://www.loom.com/share/66d37da1d31940c39691f04d7e695e0a

This issue can be related to vercel/next.js#54708. App dir router memory consumption is significantly higher then for Pages dir, but this does not affect production build, this is only dev server problem. It can be temporarily fixed by adding NODE_OPTIONS="--max-old-space-size=8192" before yarn dev command. We are researching if there is better fix for this.

[zomars]

changes addressed