Record parameter matching usage in build metadata (#99594)
## Summary
The experimental parameter matching APIs may not yet be supported by
some hosts that package Next.js builds without adapters. Add an optional
`__private_unstable_hasParamMatching: true` field to
`prerender-manifest.json` so those hosts can temporarily detect API
usage and warn about unsupported deployments rather than infer it from
generated routing behavior.
The field records evaluated layout and page exports, including
generators, empty fragments, and overridden configuration. It is omitted
when matching configuration was not evaluated and disappears when
rebuilding after the last export is removed.
This private field is temporary and will be removed; it is not a lasting
API-usage signal.
This is host-neutral metadata only: it adds no deployment restriction,
changes no runtime behavior, and does not change the public adapter
interface.
## Verification
- Production fixture passes with Turbopack and webpack: 6 cases each
covering usage, absence, and rebuild cleanup.
- An ordinary full `next build`, without route filtering, also emits the
marker.
- Type checking and formatting/lint checks pass.
<!-- NEXT_JS_LLM -->
