Bump got and firebase-tools

[dependabot]

Removes got. It's no longer used after updating ancestor dependency firebase-tools. These dependencies need to be updated together.

Removes got

Updates firebase-tools from 7.16.2 to 12.2.1

Release notes

Sourced from firebase-tools's releases.

v12.2.1

• Gracefully close rules runtime on storage emulator stop (#4902)
• Always assume build target of production when deploying a web framework, unless overridden (#5892)

v12.2.0

• Update error message when function deploy fails due to quota. (#5867)
• Fixes RTDB emulator 127.0.0.1 namespace resolution bug. (#5863)
• Improves RTDB emulator to GCF emulator network reliability. (#5863)
• Allow for Angular developers to both target a PWA and leverage serveOptimizedImages. (#5716)
• Multi-page applications that are fully staticly rendered are no longer treated as PWAs. (#5716)
• Add fast dev-mode support for devlopers using Nuxt v2. (#5716)
• Respect ssr: false and baseURL when using Nuxt. (#5716)
• Fix bug where JS SDK auto-init was not working for Vite while in dev-mode (#5610).
• Respect FIREBASE_FRAMEWORKS_BUILD_TARGET environment variable to override the default build target (#5572).
• Improves cleanup process when reloading emulated functions in debug mode. (#5878)
• Allow Web Frameworks to target NodeJS v20. (#5879)

v12.1.0

• Fixes an issue running firebase emulators:start when Python Cloud Functions directory path has spaces. (#5854)
• Add support for nodejs20 for Cloud Functions for Firebase. (#5837)
• Add Flutter Web as an option in "firebase init hosting" (#5864)
• Some failures while building Web Frameworks were not being caught (#5864)

v12.0.1

• Fixes an issue in the EventArc emualtor where events missing optional fields would cause crashes. (#5803)
• Fixes an issue running firebase emulators:start and firebase deploy when Python Cloud Functions directory path has spaces. (#5830)

v12.0.0

• Breaking: drops support for running the CLI on Node.js v14.
• Adds ext:dev:* commands to publish and manage Extensions. For step-by-step instructions on how to publish your own Extensions, see https://firebase.google.com/docs/extensions/publishers/get-started.
  • Note: These commands were previously available to early access users behind an experiment flag. There are some breaking changes from the early access version of these commands.
  • ext:dev:publish has been renamed to ext:dev:upload. ext:dev:upload defaults to uploading extensions from GitHub instead of local source.
  • ext:dev:publish is deprecated and will be removed in version 13.
  • ext:dev:delete, ext:dev:unpublish, ext:sources:create and ext:dev:emualtors:* have been removed.
• Support for Next.js i18n, basePath, and more advanced rewrites/redirects/headers (#5788)
• hosting.frameworksBackend now respects omit: true (#5788)
• Web Frameworks now memoizes framework builds for single builds across multiple hosting sites (#5788)
• Add support for Angular i18n and baseHref (#5774)
• Trip the backend requirement for Angular applications using ng-deploy w/serveOptimizedImages (#5774)
• Fixes a bug where the Storage emulator would not fall back to open rules for 'demo-' projects if firebase.json contained multiple storage targets (#5170)
• Updates firebase init function templates for TypeScript and Javascript to 2nd gen (#5775)
• Allow for atomic deployment of Hosting content & Functions rewrites via tag pinning (#5753)

v11.30.0

• Added more helpful error messages for the Firebase Hosting GitHub Action (#5749)
• Upgrade Firestore emulator to 1.17.4
• Web Frameworks will no longer try to deploy unsupported versions of NodeJS to Cloud Functions (#5733)
• Fixes bug where emulators would not start correctly due to corrupted ZIP files. (#5614, #5677)
• Adding experimental support for deploying Flutter Web applications to Firebase Hosting (#5332)
• Release Emulator Suite UI v1.11.6 (#5769)

... (truncated)

Commits

• ea96994 12.2.1
• 14b0755 Update default Storage rules to contain example cross-srevice-rules (#5298)
• 68c71b1 Always assume build target of production on deploy (#5892)
• ff2b2b2 gracefully close rules runtime (#4902)
• acdf5e4 [firebase-release] Removed change log and reset repo after 12.2.0 release
• 5c03bf5 12.2.0
• cbd92e8 Allow web frameworks to target Node v20 (#5879)
• 7909fc6 Improves cleanup process when reloading emulated functions in debug mode. (#5...
• 4c5d8c9 Adding package-lock.json to standalone/ (#5882)
• a6657df Fix Vite js-sdk auto init (#5610)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.