test: migrate Pages Router deploy exclusions to force gates (#98157)
## Summary
Migrate the remaining Pages Router, API route, i18n, custom route,
rewrite, redirect, and error-page deployment exclusions to `@force-gate`
and remove their `skipDeployment`/`skipped` control flow. This stack is
rooted at canary and independent of #98430; it preserves deployment
coverage already enabled on canary.
The custom-app-render and client-max-body-size files covered by #98994
and #98911 are omitted.
## Verification
- Compared test registration against canary in development, production,
and deploy modes with test bodies and hooks disabled (Webpack). Existing
active deployment assertions are preserved; development/production test
selection is unchanged apart from replacing empty skip placeholders with
skipped real tests.
- TypeScript, Prettier, and ESLint checks passed. Registration probes
use a default config for lazy predicates and do not exercise fixture
setup or test bodies.
- Full bootstrap attempted, but the local native SWC build fails at
`cargo metadata` with `EPERM`; full integration/deployment execution
remains for CI.
<!-- NEXT_JS_LLM -->
---------
Co-authored-by:
Jamiboy Mohammad <jamiboym@gmail.com>
Showing
Please
register
or
sign in
to comment