Tableau Dual JVM tweaks

[jdunkerley]

Pull Request Description

First PR following up on #14607

• Small fix for File.new widget.

• Renamed In_Memory_Test_Helpers to In_Memory_Helpers.

• Make use of get_java_table more explicitly from the helper class.

• StorageType "localisation" should be internal

  • Removed from Storage.to_value_type.
  • Temporarily added a makeLocalType method to help with this.
    Currently in Java_Problems and In_Memory_Column_Implementation.

• In_Memory_Table.java_table should always be within the primary runtime.

  • Removed classes being passed.
  • HyperFormat.writeTable takes an array of names and an array of storages (ColumnStorage interface).

• Altered external use of Java Column and Table to only use the ColumnStorage.

• Removed redundant helper methods.

• Pass names and storages and avoid passing the Table object.

Next PR: Overhaul exception handling.

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.

[JaroslavTulach]

I'd improve encapsulation with private especially in methods that return Java classes not transferable over dual JVM boundary

[JaroslavTulach]

• there is a std-tests failure
  • testing infrastructure created by Testing EnsoMeta ability to load Enso types from Standard.Base #14287
• probably ProblemAggregator can no longer be null...

• enso/std-bits/tests/src/test/java/org/enso/base/polyglot/tests/LongStorageTest.java

  Line 89 in 603df36

  var b = Builder.getForLong(IntegerType.INT_64, size, null);

• probably replace by a call to problemAggregator() defined at the end of the test

[JaroslavTulach]

• wow, this is relaying on a fact that statements that yield Error terminate block execution!
  • e.g. it uses Promote broken values instead of ignoring them #11777
• by having if_then only (and not if_then_else) you eliminate one indentation level
• but it feels less FP-like... which is probably not a problem at all