Ready for Release

#1132

Strict resolver

Default Strict Resolver Summary This RFC proposes shipping a built-in (opt-in) strict resolver as the default in Ember applications, replacing the current ember-resolver package. The strict resolver uses explicit module registration through import.meta.glob('...', { eager: true }) (or manually) instead of dynamic string-based lookups, providing better tree-shaking, build-time optimization, and improved developer experience with static analysis tools. Motivation The current ember-resolver requires that an Application has a modulePrefix, and that every resolver registration begins with that modulePrefix. As we start to move towards strict ESM applications, this requirement is unneeded. Previously, if folks