Polyfill @ember/owner imports for min-supported scenario

`min-supported` installs `ember-source: ~4.2.0` but the test-app's
default `@glimmer/[email protected]` has `import { setOwner } from
'@ember/owner'`. `@ember/owner` didn't ship as a module path until
ember-source 4.10, so rollup fails with:

    [vite]: Rollup failed to resolve import "@ember/owner" from
    ".../@glimmer/[email protected]/node_modules/@glimmer/component/dist/index.js"

Use `babel-plugin-ember-polyfill-get-and-set-owner-from-ember-owner` to
rewrite those imports back to `@ember/application` (which had `getOwner`
/`setOwner` in every 4.x release). The plugin only runs when
`ENABLE_COMPAT_BUILD` is set, next to babel-plugin-debug-macros. It's a
no-op for scenarios that still resolve `@ember/owner` natively
(ember-lts-5.12 and later) because `@ember/application` re-exports the
same symbols there.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Author: NullVoxPopuli

pnpm-lock.yaml

@@ -54,6 +54,7 @@ export default {
               flags: [{ source: '@glimmer/env', flags: { DEBUG: true } }],
             },
           ],
+          'babel-plugin-ember-polyfill-get-and-set-owner-from-ember-owner',
         ]
       : []),
   ],

test-app/babel.config.mjs

@@ -36,6 +36,7 @@
     "@babel/plugin-transform-runtime": "^7.29.0",
     "@babel/plugin-transform-typescript": "^7.28.6",
     "babel-plugin-debug-macros": "^0.3.4",
+    "babel-plugin-ember-polyfill-get-and-set-owner-from-ember-owner": "^1.0.4",
     "@ember/string": "^4.0.1",
     "@ember/test-helpers": "^5.4.1",
     "@embroider/core": "^4.4.7",