Add parser for line by line processing

[jdunkerley]

Pull Request Description

• ✅Linting fixes and groups.
• ✅Add File.from that:Text and use File conversions instead of taking both File and Text and calling File.new.
• ✅Align Unix Epoc with the UTC timezone and add converting from long value to Date_Time using it.
• ❌Add simple first logging API allowing writing to log messages from Enso.
• ✅Fix minor style issue where a test type had a empty constructor.
• ❌Added a long based array builder.
• Added File_By_Line to read a file line by line.
• Added "fast" JSON parser based off Jackson.
• ✅Altered range to_vector to be a proxy Vector.
• ✅Added at and get to Database.Column.
• ✅Added get to Table.Column.
• ✅Added ability to expand Vector, Array Range, Date_Range to columns.
• ✅Altered so expand_to_column default column name will be the same as the input column (i.e. no Value suffix).
• ✅Added ability to expand Map, JS_Object and Jackson_Object to rows with two columns coming out (and extra key column).
• ✅ Fixed bug where couldn't use integer index to expand to rows.

Important Notes

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,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

[radeusgd]

I've been adding a similar conversion as part of #8809 work, I think it may be worth discussing some future improvements for it as we actually may want to support not only local paths but also e.g. s3:// paths as well, if AWS is imported.

My idea is to do a File_Like.from (that:Text) = ... that would rely on a ServiceProvider logic that allows to register new protocols for resolving files.

[jdunkerley]

Happy for us to end up with that once yours is ready just felt a good change to get rid of all the File.new dotted about and use the conversion point to catch on the way through.

[JaroslavTulach]

Isn't File a builtin? If so, then it is backed by TruffleFile and not java.io.File. TruffleFile allows any kind of FileSystem including S3, once somebody writes it.

[radeusgd]

Interesting, I think we were not aware of this. We may consider going in this direction, but right now we are not handling S3 at builtin level, but as a separate type (S3_File), same as our cloud files (Enso_File).

This approach does allow us to do some more special handling for these special files and have better control of what is supported and what is not. For example, the S3_File holds AWS credentials associated to it, in case the user is working with files from different accounts, I don't think that would be possible to implement something like that using the TruffleFile abstraction.

[radeusgd]

Ah, moreover - S3 support is included in a separate library (Standard.AWS) as it should not really be part of Base.

[jdunkerley]

I do think we should investigate the options of a FileSystem but that is one for a little down the road.