[233] Untrack generated configure/public/toolConfigs.json

[CarsonDavis]

Closes #233

configure/public/toolConfigs.json is listed in .gitignore (line 17), but the rule has never applied: the configure-beta rewrite (NASA-AMMOS#574, 2024) moved the generated manifest to this path while the gitignore still pointed at the old /config/pre/toolConfigs.json location, so the file was committed unignored. When the cleanup in NASA-AMMOS#831 (2025) fixed the gitignore path, the file was already tracked — and git ignores ignore-rules for tracked files. Every server start and build regenerates it via updateTools(), so feature branches kept accidentally committing generated churn (e.g. 4708dc68, 8737cb4a).

This PR drops the file from the index (git rm --cached) with no code changes. The existing gitignore rule takes over, matching how its sibling componentConfigs.json (same generator, .gitignore:18) is already handled.

Why nothing breaks:

• Regenerated on every server start (scripts/server.js:699) and every build (scripts/build.js:57), before anything reads it
• Consumed only at runtime — the Configure app fetches it over HTTP, served by express.static from the source directory; no build-time import exists
• Docker runs npm run build (which regenerates it) before the Configure build, so a clean context is safe
• Unit tests mock the tool configs; no CI workflow references the file

Note for teammates: pulling this deletes your local copy of the file. It regenerates on your next npm start or npm run build.