Attempts to fix #24201, vibe coded

● Root Cause

When an enum companion object extends a class with by-name parameters and uses named arguments out of order:

abstract class Foo[T](defaultValue: => T, arg1: Int = 1, arg2: Int = 2)

enum Baz:
case E1, E2

object Baz extends Foo[Baz](Baz.E1, arg2 = 2) // arg1 uses default, arg2 is named

The compiler desugars the named arguments into a Block with local defs:

object Baz extends {
def defaultValue$1 = Baz.E1 // local method for first arg
def arg1$1 = 1 // local method for default value
new Foo(defaultValue$1, arg1$1, 2)
}

The problem occurs in two stages:

1. Baz.E1 wasn't being hoisted: The original refNeedsHoist didn't detect that Baz.E1 references the companion module being constructed. So Baz.E1 stayed as-is in defaultValue$1's body.
2. Closure captures uninitialized this: When ElimByName wraps the by-name argument in a closure () => defaultValue$1, this closure needs to call defaultValue$1() which is an instance method on this. But this isn't initialized until after the super constructor runs → VerifyError.

Why The Fix Works

Fix Part 1: Detect self-references

tp.symbol == cls || tp.symbol == cls.companionModule || refNeedsHoist(tp.prefix)
Now Baz.E1 is correctly detected as needing hoisting because Baz (the prefix) refers to cls (the module being constructed). This creates a static method Baz$$superArg$1() that returns Baz.E1.

Fix Part 2: Inline hoisted calls

When processing the Block, if a local def's RHS was hoisted (e.g., defaultValue$1 = Baz$$superArg$1()), we track this in inlinedDefs. Then when creating the body of any subsequently hoisted method, we replace references to defaultValue$1 with Baz$$superArg$1() directly.

Result: The closure body becomes () => Baz$$superArg$1() instead of () => defaultValue$1. Since Baz$$superArg$1() is a static method, no this capture is needed → no VerifyError.

The static method hoisting technique already existed in HoistSuperArgs - that's the entire purpose of the phase.