Resolve variables at parse time

[stackoverflow]

This replaces ResolveVariableNode and ResolveMethodNode with their resolution. When we build the truffle node tree, we determine whether names resolve to:

• lexical scope
• base module
• implicit this

Then, we use this information to directly construct the underlying nodes (ReadPropertyNode, ReadLocalPropertyNode, etc).

Additionally, AstBuilder determines whether the property access must be const or not.

This introduces a BaseModuleMembers registry, which gets generated as part of Java compilation.

Closes #1154

NOTE: this introduces a regression in the REPL. Currently, this works:

pkl0> foo { bar = baz }
pkl1> local baz = 3
pkl2> :f foo
new Dynamic {
  bar = 3
}

Now, :f foo produces an error, because baz is resolved to implicit this.

[bioball]

Currently, amends "..." REPL statements don't do anything. In this PR, the header still mostly does nothing, but it will throw if the amends has a relative path.

This is because our REPL logic has changed; before the AstBuilder can visit an expression, it first needs to visit the module to collect names. In the process of visiting the module, it will validate this module header.

[bioball]

Optimization: move logic around finding the enclosing frame into its own node so that we don't keep re-executing the traversal logic every time we get a FrameSlotTypeException

[bioball]

This is an existing TODO, not newly introduced by this PR (GitHub isn't able to track that the code just got shuffled around).

[bioball]

When we resolve frame slot variables, we need to know the names of each slot. The FrameDescriptor.Builder API keeps these names inside private fields. So, we use our own builder abstraction that exposes the slot names.

[bioball]

This generates a class called BaseModuleMembers, and gets called as part of java compilation.

This generates a class that looks something like:

public final class BaseModuleMembers {
  private BaseModuleMembers() {
  }

  public static boolean hasProperty(String name) {
    return switch (name) {
      case "AlsoKnownAs",
        "Annotation",
        "Any",
        "BaseValueRenderer",
        "Boolean",
        "Bytes",
        "BytesRenderer",
        "Char",
        "Charset",
        "Class",
        "Collection",
        "Comparable",
        "ConvertProperty",
        // etc
        "YamlRenderer" -> true;
      default -> false;
    }
  }
}

This is used by SymbolTable to figure out if some name is defined on the base module or not.
This is much faster than looking up members on BaseModule.getModule().