test(firestore): use TARGET_DATABASE_ID in lifecycle integration tests

[wu-hui]

Summary

Pass BuildConfig.TARGET_DATABASE_ID to FirebaseFirestore.getInstance(app, BuildConfig.TARGET_DATABASE_ID) in testRestartFirestoreLeadsToNewInstance() and testAppDeleteLeadsToFirestoreTerminate().

Context

When running Nightly integration tests against the regional us-central1-test-firestore.sandbox.googleapis.com endpoint (TARGET_DATABASE_ID="enterprise" in us-central1), calling FirebaseFirestore.getInstance(app) defaults to the (default) database (located in nam5), causing network writes in these two lifecycle tests to time out.

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

[google-oss-bot]

Did you forget to add a changelog entry? (Add the 'no-changelog' label to the PR or 'NO_RELEASE_CHANGE' to the description to silence this warning.)

[github-actions]

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.