chore: Upgrade to React 19

[evadecker]

What changed?

Upgrade from React 18.3 to React 19.

Why?

It's stable!

How was this change made?

Upgraded React and related packages and types. Replaced motion with an alpha version of framer-motion to support React 19 types until motion is updated, see motiondivision/motion#2843 (comment)

How was this tested?

Automated testing, everything passes.

Anything else?

Will follow-up with updated action hooks: https://react.dev/blog/2024/12/05/react-19

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7fa6639

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	33.26% 🟰 ±0%	1855 / 5577
🔵	Statements	33.26% 🟰 ±0%	1855 / 5577
🔵	Functions	29.84% 🟰 ±0%	57 / 191
🔵	Branches	61% 🟰 ±0%	97 / 159

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
src/main.tsx	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	0% 🟰 ±0%	1-106
src/components/common/AnimateChangeInHeight/AnimateChangeInHeight.tsx	6.89% 🟰 ±0%	100% 🟰 ±0%	0% 🟰 ±0%	6.89% 🟰 ±0%	11-44

Generated in workflow #188 for commit e71b1e8 by the Vitest Coverage Report Action

[cloudflare-workers-and-pages]

Deploying namesake with    Cloudflare Pages

Latest commit:	e71b1e8
Status:	✅  Deploy successful!
Preview URL:	https://1ee1753c.namesake-639.pages.dev
Branch Preview URL:	https://react-19.namesake-639.pages.dev

View logs