Eliminate per-call closure for InlineIfLambda partial applications

[T-Gro]

Passing a partial application of a module-level function to an [<InlineIfLambda>] parameter allocated an FSharpFunc closure per call whenever a captured argument was non-trivial (a field read, a call): the optimizer only beta-reduces a lambda-valued argument whose optimization info is a syntactic lambda, and a partial application carries UnknownValue. The argument is now eta-expanded to a lambda with its captured evaluations floated above the binding, so the parameter's uses beta-reduce and the closure is eliminated. Captured arguments are still evaluated exactly once, in order. This generalizes the single call site hand-fixed in #20426 to every such site.

xs |> Option.map (f a b.Value)
// before: allocates an FSharpFunc closure capturing `b.Value`, per call
// after:  `b.Value` is read once and `f` is called directly — no closure

Self-compiling FSharp.Compiler.Service.dll (no closure-count change in FSharp.Core, FSharpPlus, IcedTasks or the compiler test suite):

FSharp.Compiler.Service self-compile	before	after
FSharpFunc closure display-classes	16224	16203 (−21)
allocated per compile	baseline	≈ 30 MiB less

The 21 eliminated closures include memberInfoR@1696 — the exact one #20426 removes by hand.

[github-actions]

❗ Release notes required

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

---

✅ Found changes and release notes in following paths:

Change path	Release notes path	Description
`src/Compiler`	docs/release-notes/.FSharp.Compiler.Service/11.0.100.md