Bugfix :: SRTP - ApplyDefaults for TyparConstraint.MayResolveMember

[T-Gro]

Fixes a regression introduced in .NET 9 SDK that caused FSharpPlus curryN-style SRTP patterns to fail with FS0030 (value restriction error).

Root Cause

The FreshenTypar function (added for Interfaces with Abstract Static Members) clears StaticReq to None when refreshing type parameters. However, ApplyDefaults in CheckDeclarations.fs only solved typars where StaticReq <> None, missing SRTP typars that have MayResolveMember constraints but no explicit static requirement set.

Fix

Extended ApplyDefaults to also solve typars that have MayResolveMember constraints, regardless of their StaticReq value.

[github-actions]

❗ Release notes required

@T-Gro,

Caution

No release notes found for the changed paths (see table below).

Please make sure to add an entry with an informative description of the change as well as link to this pull request, issue and language suggestion if applicable. Release notes for this repository are based on Keep A Changelog format.

The following format is recommended for this repository:

* <Informative description>. ([PR #XXXXX](https://github.com/dotnet/fsharp/pull/XXXXX))

See examples in the files, listed in the table below or in th full documentation at https://fsharp.github.io/fsharp-compiler-docs/release-notes/About.html.

If you believe that release notes are not necessary for this PR, please add NO_RELEASE_NOTES label to the pull request.

You can open this PR in browser to add release notes: open in github.dev

Change path	Release notes path	Description
src/Compiler	docs/release-notes/.FSharp.Compiler.Service/11.0.100.md	No release notes found or release notes format is not correct

[T-Gro]

/run ilverify

[github-actions]

🔧 CLI Command Report

• Command:/run ilverify
• Outcome: success

✅ Command succeeded, no changes needed.