Avoid false FS1113 on inline instance members with class-scope self identifiers

[Copilot]

Inline instance members in classes currently fail with FS1113 when a class-scope self identifier is present (type C() as self = ...), even though the member body is valid. This change removes that false-positive path while preserving FS1113 behavior for non-member inline values.

• Compiler behavior change (Optimizer)

  • Updated inline-completeness enforcement to apply only to non-member values.
  • CheckInlineValueIsComplete now skips the IsPartialExprVal/FS1113 check when v.IsMember is true.

• Regression coverage (ComponentTests)

  • Added a focused test in MemberDeclarations covering the three reported forms:
    • class-scope self + different member self identifier
    • class-scope self + same member self identifier
    • class-scope self + _ member self identifier

type TestClass1() as SomeSelfIdentifier =
    member inline AnotherSelfIdentifier.test() = 5

type TestClass2() as self =
    member inline self.test() = 5

type TestClass3() as self =
    member inline _.test() = 5

[T-Gro]

The fix is correct. Class-scope self identifiers (as self) produce UnknownValue in the optimizer representation, causing spurious FS1113 for inline members. Skipping the check for all members via not v.IsMember is sound because:

1. Accessibility for inline members is already enforced by FS0044 at type-check time
2. Partial optimizer data for members is expected (self-parameter handling) and doesn't indicate a broken inline
3. The internal error at line 4217 still guards against truly unresolvable inline data

The test covers the three reported forms cleanly. LGTM.

[github-actions]

❗ Release notes required

---

✅ 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

[T-Gro]

/azp run fsharp-ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).