chore(firestore-bigquery-export): Restore kit dependencies for firebase-admin and firebase-functions.

[ajperel]

Changed as part of testing the workflow to flip dependencies to peer
during release.

[gemini-code-assist]

Code Review

This pull request moves firebase-admin and firebase-functions from devDependencies and peerDependencies to direct dependencies in kits/firestore-bigquery-export. However, using the pre-release version ^7.3.3-rc.3 for firebase-functions prevents proper deduplication, leading to a duplicate nested installation of version 7.3.2 under @firebaseextensions/firestore-bigquery-change-tracker. Since firebase-functions relies on global state, this duplication can cause runtime initialization or deployment failures. It is recommended to use a stable version of firebase-functions to allow proper deduplication.

[gemini-code-assist]

⚠️ Duplicate firebase-functions Versions in Dependency Tree\n\nHaving multiple versions of firebase-functions (root at 7.3.3-rc.3 and nested at 7.3.2 under @firebaseextensions/firestore-bigquery-change-tracker) can lead to severe runtime issues. firebase-functions relies on global/singleton state for trigger registration and configuration; having duplicate instances of the module at runtime often causes silent deployment failures or initialization crashes (e.g., duplicate app initialization errors).\n\n#### Why this happens:\nUnder standard semver rules, the pre-release version 7.3.3-rc.3 does not satisfy the stable range ^7.3.0 required by @firebaseextensions/firestore-bigquery-change-tracker. As a result, npm resolves and installs a nested stable version (7.3.2), bypassing the deduplication process.\n\n#### Recommendation:\nConsider using a stable version of firebase-functions (e.g., ^7.3.2) in package.json to allow proper deduplication, or ensure that the override strictly forces a single version without causing nested duplication.