simplify trees that appear in tastycheck test (#21274)

unfortunately it seems changing the classpath means representation of
TASTy is not stable (but is semantically equivalent) i.e. some
SHAREDtype might be replaced by equivalent types. This breaks the
tastycheck test in #21214 with scala
2 library tasty.

By changing to ordinary classes instead of enum cases, we limit
generated code and avoid these specific examples of instability in the
test.

Manually, I confirmed that reverting the change to namer in #21214 still
breaks the new test

[test_scala2_library_tasty]

Author: hamzaremmal

tests/pos/i21154/Z.scala

@@ -3,7 +3,9 @@
 // in the original issue https://github.com/scala/scala3/issues/21154, the non-deterministic tasty
 // depends on the order of compilation of files, the use-site (A.scala) has to come first,
 // and the file defining the enum has to come second (Z.scala), A.scala in namer will force Z to complete.
-enum Z:
-  case AOptions()
-  case BOptions()
-  case COptions()
+sealed trait Z
+
+object Z:
+  class AOptions() extends Z
+  class BOptions() extends Z
+  class COptions() extends Z