chore: upgrade Rspack and Module Federation ecosystem

[ckken]

Scope

• Changed areas: Rspack/Rsbuild/Rslib/Rstest, Rsdoctor, SWC, html-webpack-plugin, ts-checker-rspack-plugin, and Module Federation MF2 dependency closure; cache.maxVersions migration; version contracts.
• Protected areas not touched: website, publish workflow, packages/cdn-, packages/lib- dependency lines. apps/test only updates the Rstest acceptance version contract.
• User-visible behavior: builds and Module Federation runtime use the current 2.2.1 / 2.9.0 stack; deprecated cache.maxVersions is ignored before passing config to Rspack.

Directory Boundary Check

• apps changes are limited to the acceptance contract required by this ecosystem upgrade.
• I did not modify packages/cdn-* or packages/lib-* version lines.
• I did not create or continue repo-local historical workflow directories.
• I did not commit generated output, caches, or local indexes.

Validation

• corepack pnpm install --frozen-lockfile
• corepack pnpm workflow:check (via ci:verify)
• git diff --check
• corepack pnpm test:toolchain (12/12)
• CLI and @empjs/share target build/tests
• corepack pnpm ci:verify
• corepack pnpm empbuild
• mf-host and mf-app production builds
• corepack pnpm test:browser:all (22 files, 31 tests)
• Independent frozen-lockfile and version-closure verification

Release Safety

• No CI or publish workflow changes.
• Release scope still excludes apps and website.
• No publish or deployment performed.

Review

• Reviewer can reproduce the validation commands above.
• Residual legacy MF 0.x and older SWC entries belong to independent lib/CDN lines and were intentionally left unchanged.