fix(angular-rspack): stats serialization and configuration

[faileon]

Current Behavior

1. Performance bottleneck: statsValue.toJson() is called with no options, causing full serialization of all stats data on every build. This is expensive and unnecessary when only budget checking is needed.
2. Redundant work: Budget checking code runs even when no budgets are configured or when targeting server platform.
3. User stats config ignored: Custom stats configuration provided via rspackConfigOverrides is not respected by the stats logger.
4. Double serialization: rspackStatsLogger calls stats.toJson() without passing the stats options, ignoring user preferences.

Expected Behavior

1. Only serialize what's needed for budget checking (assets and chunks), significantly reducing overhead.
2. Early exit when budgets are not configured or on server platform, skipping expensive toJson() entirely.
3. User's stats configuration is merged with defaults and respected throughout the build output.
4. rspackStatsLogger uses the provided statOptions when serializing stats.

Related Issue(s)

Fixes #34145

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	b5026f4

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
nx-dev	Ready	Preview	Jan 20, 2026 4:45pm

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b5026f4

Command	Status	Duration	Result
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	2m 36s	View ↗
nx affected --targets=lint,test,test-kt,build,e...	✅ Succeeded	1m 56s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	11s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	3s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-01-20 17:22:09 UTC

[Coly010]

Hey @faileon The merge of one of the other PRs has led to a conflict here :)

[faileon]

Hey @faileon The merge of one of the other PRs has led to a conflict here :)

I have resolved the merge conflicts and pushed an update to my forked repo.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.