(cherry picked from commit 63df7b5)

While generating link to route "dynamicWithChild.child": can't access
property "shouldSupercede", newHandlerInfo is undefined

LinkTo needs route context to allow omitting model from current active
route. Without the guard, tests where LinkTo rendered in tests without
routing transition started will break. See issues/19364

Upgrades Glimmer VM, removing template ids

Removes template ids

This PR refactors the internal Ember loader so that it uses the standard
Ember CLI loader instead for modules. This means that modules will be
defined in the main namespace, and importable from there, instead of in
a hidden namespace that only Ember can use.

Notes:

- Code is still loaded and built via `treeForVendor` and included as a
  vendor file. This needs to be the case for the time being for
  bootstrapping.
- Loader code is still included for Node support. If `define` and
  `require` are not already defined, then a backup shim is used instead.
- Modules are now exposed from Ember, but `ember-cli-babel` still
  transpiles them to global references. This unblocks us from being able
  to make all modules work normally, however.
- `require` shim module is no longer defined, we reference `define` and
  `require` as globals instead (which is more accurate). In the future
  we should update this to use Embroider's conventions.
- `__loader` is still exposed on the Ember object, referencing the same
  values as before.

Refactor the internal Ember loader to use the standard Ember CLI loader

In 3.24.0-3.24.2 we made changes to let LinkTo href generation returns
empty when initial transition is not started. This is not true and
causing regression on the super-rental tutorial.

In previous tutorials, the LinkTo component will return empty href when
`this.owner.setupRouter()` is not called. It generates valid href if
`setupRouter()` is called and complete model are passed for dynamic
segments.

In our previous changes, we removed the requirement to call
`setupRouter`, and always return empty href when initial transition is
not started. This is not expected when passing complete dynamic segments
without initial transition.

…-rerender-assertion

[CLEANUP] Adds extra test for new rerender assertion

Ensures the `registry` field on `Ember.__loader` is setup properly, and
that the shim loader has `entries` defined on it correctly.

…lable

[BUGFIX] Ensure entries are properly defined on loader

[BUGFIX lts] Force building Ember bundles when `targets.node` is defined

(cherry picked from commit dd26c4e)

(cherry picked from commit 98745fb)

(cherry picked from commit 647279b)

From #19406

Add test to ensure helpers are computed lazily (when used)

…iers

Updates the VM, which includes a fix for dynamic helper and modifier usage.

Release notes: https://github.com/glimmerjs/glimmer-vm/releases/tag/v0.77.0

…med-arguments

[DOC] Correctly mark public link-to component named arguments

* use async functions
* use native class syntax
* shortern the test names
* avoid `assert.expect`
* avoid soon-to-be-deprecated `@id` argument

[INTERNAL] refactor <LinkTo> tests

Was also affecting a heading anchor link. Kudos to @kaermorchen.

Refactor link-to transitioning-classes tests

* Cleanup TypeScript
* Add `expectNoDeprecationAsync`
* Add `isEnabled` flag to replace `maybeExpectDeprecation`

[INTERNAL] Refactor `expectDeprecation` and friends

…deprecation

Fix glimmer-component-docs.ts typo in Markdown

…d-component-test-blueprints

Use qunit-dom in helper and component test blueprints