feat: Allow @elideTypeInfo as an attribute

[spotandjake]

This PR adds a new @elideTypeInfo attribute. It is similar to eliding type information at the CLI level, but is intended more for use within the runtime or library internals where we only want to elide type information from specific parts of a program.

The attribute can be applied in the following places:

Above a record definition:

• Elides the type information for that record specifically.

Above an enum definition

• Elides the type information for that enum specifically.

Above a submodule definition:

• Elides the type information for everything within the submodule.

Above a module definition:

• This might initially seem equivalent to eliding type information for the entire program, but it only affects the module itself.
• For example, if you have a Main module with type information elided, you can still print records from other modules where type information has not been elided.

It should be pretty easy in the future to enable this on exceptions as well, but that requires a parser change to allow attributes above exception definitions.

While working on #2385, I noticed that a significant portion of the added program size came from the use of higher-level types such as records and enums. Some of that additional size comes from the type information associated with those types.

The intention of introducing this attribute is to give us a more selective way to strip type information from specific modules, submodules, records or enums. This is particularly useful for runtime and internal library code where we know that the type information will never be needed, and want to reduce the size of the resulting program or in the case of the runtime want to ship slim libraries.

Closes: #2365

[Kara-Zor-El]

took a quick look tonight. Also, side note but in general i think it might make more sense to change elide to omit in this and in general. I do think its more common in everyday language and would increase clarity.

[Kara-Zor-El]

is there a reason these aren't prepended to the error list and instead replaces it?

[Kara-Zor-El]

same as above

[Kara-Zor-El]

you should probably add tests for elideTypeInfo at a file level and maybe testing calling toString on a type in one file from another

[Kara-Zor-El]

these two cause toString/print to change

module Main

from "path" include Path

let p = Path.fromString("/file.txt")
print(p)

goes from

AbsoluteFile(({
  base: Abs(Root)
}, {
  fileType: File
}, ["file.txt"]))

to

AbsoluteFile(({
  base: Abs(Root)
}, <record value>, ["file.txt"]))