fix: generated eslint config only imports what package.json installs

[spencer-osbrjp]

Closes #118

Root cause

templates/linter/eslint/eslint.config.mjs.tmpl imported globals, typescript-eslint, eslint-plugin-react-hooks, and eslint-plugin-react-refresh unconditionally, but the registry's eslint entry only ships eslint + @eslint/js, and the react-plugin dependency rule fired only for vite-react. Every other base (the reporter used plain Astro) hit Cannot find package on its first husky pre-push lint. The **/*.{ts,tsx,vue,astro} glob also fed .astro/.vue files to a config with no matching parser.

Fix

• globals + typescript-eslint move into the registry's eslint entry — an unconditional import is an unconditional dependency.
• The react plugin imports are wrapped in the template's existing IsReactInt condition, and the dep rule now tracks the same condition (vite-react and astro-react, which was silently broken too).
• The lint glob narrows to **/*.{ts,tsx} — matching what the shipped config can actually parse.

Plain-Astro output now matches the issue's "working config" verbatim.

Preventing the class

New TestGeneratedConfigImportsAreInstalled: scaffolds nine representative combos (every base × eslint, ox tooling, playwright, defaults) and asserts that every package imported by a generated top-level config file is installed by the generated package.json. Any future template/registry drift of this kind fails CI instead of the user's first push.

Testing

go test ./... green (the new guard test fails on the pre-fix templates for astro/astro-vue/vite-vue/nuxt/astro-react). E2E: scaffolded -t astro, confirmed the rendered config and devDependencies line up.

🤖 Generated with Claude Code

[spencer-osbrjp]

Second commit widens the fix to the root cause the first one exposed: BaseFramework.GetIntegration had an inverted nil check (returned an error whenever the registry WAS loaded), so IsReactInt/IsVueInt always returned false — the eslint template's react branch could never fire, and IsVueInt also compared against "react". Both repaired, with tests pinning every base's integration helpers and the positive react-plugin wiring (config imports and installed deps). The remaining pre-existing gap found nearby (BumpRegistry skipping backend/orm/database) is filed separately as #122.