Fix #24573: Add stricter checks for platform SAM compatibility

[noti0na1]

This PR fixes issue #24573 by adding stricter checks for platform SAM compatibility.

The regression issue starts from version 3.8.0 where Function1 and related traits gained the NoInits flag (I guess due to the way we read from jvm bytecode or from tasty?).
This changes how the compiler determines whether a SAM type qualifies as a platform SAM. When a trait is classified as a Java platform SAM, the compiler uses invokedynamic with LambdaMetaFactory (LMF) to create the lambda at runtime, rather than expanding it into an anonymous class at compile time. This is more efficient, but LMF has limitations on what type adaptations it can perform automatically.

It turns out the logic regarding SAM traits extending other traits has problems from the beginning, and even in Scala 2. The code from the issue works before 3.8 is totally by accident (because we always expand the SAM trait extending FunctionN).
We can reproduce the runtime exception using a custom function class (in Scala 2, and Scala 3.0~8):

trait F1[-T, +R]:
  def apply(t: T): R

trait SF[-T] extends F1[T, Unit]:
  def apply(t: T): Unit

@main def Test =
  val sf: SF[String] = i => println(i)
  sf("") // exception here
  // Caused by: java.lang.invoke.LambdaConversionException: 
  //Type mismatch for lambda expected return: void is not convertible to class java.lang.Object

From the view of Scala, SF is a valid SAM, because it has one abstract function def apply(t: T): Unit. However, after erasure, the apply of F1 becomes Object apply(Object), and the apply of SF becomes void apply(Object), which are two different abstract functions; hence, SF is not qualifies as a function interface on JVM. This is not only for Unit type, any primitive number type can cause the similar problem.

Therefore, we have to expand the rhs of val sf: SF[String] = i => println(i) into an anonymous class and implement all the bridge functions.

This PR strengthen the SAM check on Java platform by adding a function called samNotNeededExpansion to check if the SAM method's erased signature is compatible with all overridden methods. It mirrors the logic in Erasure.Boxing.adaptClosure to determine what LMF can and cannot auto-adapt.

[noti0na1]

Still WIP

[bracevac]

Suggested change

	def samNotNeededExpansion(cls: ClassSymbol)(using Context): Boolean = cls.typeRef.possibleSamMethods match
	def samExpansionNotNeeded(cls: ClassSymbol)(using Context): Boolean = cls.typeRef.possibleSamMethods match