When we use a lambda class, we implicitly instantiate it. That
constitutes a static dependency, which we previously failed to
register.

Fix #5159: Register static module dependency on used lambda classes.

* Move it to `frontend`.
* Make it public.
* Move the logic of `validate` and `transformLinkTimeProperty` to
  their respective call sites.
* Construct them from a CoreSpec, rather than being contained by CoreSpec.

These changes better isolate the data (`LinkTimeProperties`) from the
transformations we apply to that data (the logic in `Analyzer` and `Desugarer`).

removeRange should throws an `IndexOutOfBoundsException` if
fromIndex or toIndex is out of range. addAll should also throw
when the index is not within bounds.

The original implementation of ju.ArrayList uses js.Array as its
internal data structure. When compiling to Wasm, operations on
ju.ArrayList require JS interop calls to access the underlying
js.Array, which causes a slow performance.

This commit introduces an implementation of ju.ArrayList for the
Wasm backend. This version uses Scala's Array instead of js.Array
for better performance.

Reorganize LinkTimeProperties.

Wasm: Implement ju.ArrayList without js.Array for Wasm backend