Remove support for `rollForwardOnNoCandidateFx` and `applyPatches`

`rollForwardOnNoCandidateFx` and `applyPatches` have not been the recommended way to configure framework resolution since .NET 3.0. We kept them for backwards compatibility, but it has been enough releases that we should remove support for them. Same with the equivalent command line and environment variable options for `rollForwardOnNoCandidateFx` (`applyPatches` is runtime config only).

`rollForwardOnNoCandidateFx` values directly map to `rollForward`:
- `0` -> `LatestPatch`
- `1` -> `Minor`
- `2` -> `Major`

`applyPatches` has no direct equivalent, but the default (true) remains the default behaviour - using latest patches is recommended. If an exact version is desired, use `rollForward` value `Disable`.

Search the runtime's framework-resolution handling for rollForwardOnNoCandidateFx and applyPatches, including runtime config, command-line, and environment-variable entry points. Verify how the legacy values map to rollForward, then run the relevant resolution tests if found. Done means the old options are rejected or ignored as intended while rollForward behavior and latest-patch defaults remain unchanged.

Written by the indexing model from the issue text.