Debug functions like check(), expect(), and unwrap() from @glimmer/debug
are meant only for local development and must not appear in any published
builds. This commit adds a Babel plugin to the build pipeline that strips
these calls from both development and production builds.

Changes:
- Add @glimmer/local-debug-babel-plugin to build pipeline
- Configure plugin to strip debug calls after TypeScript compilation
- Remove build-verify.mjs and its CI reference as debug stripping is now automatic
- Work around pnpm ecosystem peer dependency conflicts in CI floating dependencies test
- Add comprehensive documentation about build constraints
- Document debug assertion usage for developers

The solution uses the existing @glimmer/local-debug-babel-plugin that
was already in the codebase but not integrated into the build process.
This ensures developers can continue using debug assertions freely while
the build system automatically removes them from published packages.

The build verification script was deleted as part of integrating automatic
debug stripping via Babel plugin. The repo metadata needs to be updated
to reflect this change.

Improve robustness of the metadata update script by adding:
- Try-catch blocks around pnpm execution and JSON parsing
- Validation that package.json files exist before reading
- Proper error messages for debugging
- Type assertions to fix TypeScript safety issues
- Replace process.exit() with thrown errors per linting rules

Also removed problematic @pnpm/* dependencies from repo-metadata
package.json and fixed the floating dependencies CI job.

Remove npm metadata artifacts that were contaminating package.json during
development (bugs, readme errors, _id, homepage, author format changes).

Exclude root package.json from package updater processing to prevent
property reordering that causes Verify CI check failures.

…tall