Builtins expose Enso methods

[Akirathan]

Closes #11589

Pull Request Description

Builtin types expose methods via the interop protocol. In fact, all types expose methods via interop protocol.

Important Notes

• Every builtin type extends BuiltinObject
  • This is enforced during annotation processing in BuiltinsProcessor.ensureBuiltinClassExtendsBuiltinObject.
• Method members are reported in Type.getMembers

The first attempt to implement hasMember and getMembers on BuiltinObject abandoned - #11687 (comment)

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[Akirathan]

Both TimeZone and Duration now have members, so we need to add these guards here.

[JaroslavTulach]

The whole EqualsXyzNode set of @Specialize annotation is fragile, unreadable, not fully testable and deserves a rewrite. At least that's the feeling I get every time I am changing the code.

Such a gentle change is OK, unless total rewrite is attempted.

[Akirathan]

See my answer in #11687 (comment) - yes it is a mess.

[JaroslavTulach]

• OK, let's integrate.

• cannot call Ref.get: https://github.com/enso-org/enso/pull/11577/files#r1848224116
• cannot call File.path on EnsoFile
• cannot call to_text on Vector - discovered while working on
  Warnings displayed after main exit do not use defined to_text #11569

• the Enso builtins don't expose Enso methods #11589 issue started with three examples of missing builtin methods
• shall we not fix some of these cases in this PR?

[JaroslavTulach]

There is a lot of Table_Tests failures like this one:

org.enso.table.error.UnexpectedTypeException: Unexpected value type. Expected a java.time.LocalTime but got com.oracle.truffle.polyglot.PolyglotMap.

[JaroslavTulach]

There is a lot of invalid sharing layer:

 Test org.enso.compiler.test.ExecCompilerTest.chainedSyntax failed: org.graalvm.polyglot.PolyglotException: java.lang.AssertionError: Invalid sharing of AST nodes detected. The current context uses a different sharing layer than the executed node. A common cause of this are CallTargets that are reused across different contexts in an invalid way.Stack trace: 

I'll try to reproduce the failures locally. When running runtime-integration-tests/test I am getting:

[info] Test run org.enso.interpreter.test.interop.TypesExposeConstructorsTest finished: 0 failed, 0 ignored, 8 total, 0.005s
[error] Test org.enso.interpreter.test.hash.HashCodeTest failed: java.lang.AssertionError: It is a time like value (Error: (Compile_Error.Error 'No polyglot symbol for org.enso.base.time.EnsoDateTimeFormatter')), took 0.0 sec
[error]     at org.enso.interpreter.test.ValuesGenerator.timesAndDates(ValuesGenerator.java:531)
[error]     at org.enso.interpreter.test.hash.HashCodeTest.fetchAllUnwrappedValues(HashCodeTest.java:80)
[error]     at org.enso.interpreter.test.hash.HashCodeTest.initContextAndData(HashCodeTest.java:52)
[error]     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
[error]     at java.lang.reflect.Method.invoke(Method.java:580)

and then also the sharing layer error latter. I'd start by fixing the first error and hoping the subsequent ones will go away.

[Akirathan]

Trying to first integrate #11835 seems like a dead end. Let's rather try a different approach - builtin objects do not expose members, but their types do. 752ac90 starts to implement hasMember and getMembers on a Type so that it returns methods as invocable members.

[Akirathan]

the
#11589 issue started with three examples of missing builtin methods
shall we not fix some of these cases in this PR?

@JaroslavTulach Ref.get, Vector.to_text, and File.path mentioned in #11589 (comment) tested in InvokeBuiltinMethodViaInteropTest

[Akirathan]

BuiltinObject super class split into a separate PR - #11861