feat(firestore): support non-default databases

[sam-ami]

Plugin(s)

• Analytics
• App
• App Check
• Authentication
• Crashlytics
• Cloud Firestore
• Cloud Functions
• Cloud Messaging
• Cloud Storage
• Performance
• Remote Config

Current problem

The current implementation of the package only supports the default Firestore instance. This limitation means users cannot specify or interact with different Firestore databases by their database ID. As a result, applications requiring access to multiple Firestore databases or specific non-default instances are restricted, reducing flexibility and scalability. This feature aims to address this issue by allowing support for Firestore by database ID, enabling users to target and manage specific Firestore databases more effectively.

Preferred solution

To address the current limitation, the package should be enhanced to include support for Firestore by database ID. This involves updating the configuration options to accept a database ID parameter, allowing users to specify which Firestore instance they want to connect to. The implementation should ensure seamless integration with the existing functionality, maintaining backward compatibility for those who continue to use the default Firestore instance. Additionally, thorough documentation and examples should be provided to guide users on how to configure and use the new feature, ensuring a smooth transition and adoption process. This solution will increase the package's flexibility, enabling it to cater to a wider range of use cases and scenarios.

Alternative options

No response

Additional context

No response

Before submitting

• I have read and followed the feature request guidelines.
• I have attached links to possibly related issues and discussions.