build: migrate embedded server to Babel 8

[chrisae9]

Summary

• upgrade the embedded server build from Babel 7 to Babel 8
• align the declared Node engine range with Babel 8's supported runtimes
• remove Babel 7's deprecated glob@7 and inflight dependency chain

Dependency status

• clean install now emits only the upstream glob@10.5.0 notice from Vue Test Utils through js-beautify
• npm audit --audit-level=high reports zero vulnerabilities
• this PR intentionally leaves Vue Test Utils unchanged because replacing its formatter chain is a separate upstream/tooling concern

Verification

• Node 24.18/npm 11: clean install, production build, 153 Node tests, 235 Vitest tests, warning-free whole-repository lint, zero-vulnerability audit, and clean diff check
• Node 22.18/npm 10: production build, 153 Node tests, 235 Vitest tests, and warning-free whole-repository lint
• Mac mini ARM64, exact commit 9d55898fadb58d985517364fdabc5b1019bddd2c: clean install, production build, 153 Node tests, 235 Vitest tests, warning-free whole-repository lint, zero-vulnerability audit, and clean diff check
• CodeRabbit review will be recorded before merge

[coderabbitai]

Warning

Review limit reached

@chrisae9, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b2008f8b-bb42-4c50-98ec-7d0b98445783

📥 Commits

Reviewing files that changed from the base of the PR and between 1c9a944 and 9d55898.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json, !package-lock.json

📒 Files selected for processing (1)

• package.json

---

_{Comment @coderabbitai help to get the list of available commands.}