[CLEAN] Synthetic Benchmark PR #26710 - chore: update dependencies

[tomerqodo]

Benchmark PR calcom#26710

Type: Clean (correct implementation)

Original PR Title: chore: update dependencies
Original PR Description: ## What does this PR do?

Resolves Dependabot alerts by updating transitive dependencies via resolutions.

Changes

Package	From	To
@modelcontextprotocol/sdk	1.24.0	1.25.2
serialize-javascript	-	6.0.2
jose	4.13.1	4.15.9
@adobe/css-tools	4.2.0	4.3.2
jsondiffpatch	0.6.0	0.7.2
min-document	2.19.0	2.19.1

Notes

• All updates are patch/minor versions with no breaking changes
• jose updated directly in apps/web/package.json and packages/features/auth/package.json (not via resolution due to incompatibility with [email protected])
• Tested 2FA login flow locally (jose is used for JWT signing/verification)

How should this be tested?

1. yarn install completes without errors
2. yarn build completes successfully
3. 2FA login flow works (uses jose for JWT)
4. General app functionality unchanged

Mandatory Tasks

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• N/A I have updated the developer docs in /docs if this PR makes changes that would require a documentation change
• I confirm automated tests are in place that prove my fix is effective or that my feature works.
  Original PR URL: chore: update dependencies calcom/cal.com#26710

[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 "[CLEAN] Synthetic Benchmark PR #26710 - chore: update dependencies". 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

[github-actions]

This PR has been marked as stale due to inactivity. If you're still working on it or need any help, please let us know or update the PR to keep it active.