[dajiaohuang]

Fixes #11447.

Database-scoped Firestore selectors now honor the optional resource suffix:

• firestore:<databaseId|target>:rules prepares and deploys only rules for that database.
• firestore:<databaseId|target>:indexes prepares and deploys only indexes for that database.
• firestore:<databaseId|target> continues to select both resources.
• Unsupported resource suffixes fail instead of being silently ignored.

Global firestore:rules and firestore:indexes selectors remain resource-specific. Comma-separated global and database-scoped selectors combine their resource selections.

Validation:

• Focused Firestore specs: 14 passing.
• ESLint on the four changed files: 0 errors; 44 warnings.
• The project TypeScript compile reports seven diagnostics in unchanged files (dataconnect-sql-shell.ts, frameworks/astro/utils.ts, gcp/cloudsql/connect.ts, and logger.ts); none reference the changed files. Full npm test was not run.

[gemini-code-assist]

Code Review

This pull request refactors and improves the Firestore configuration parsing and resource selection logic during deployment. It introduces support for database-scoped resource targets (e.g., deploying only rules or indexes for a specific database) and simplifies the preparation step by centralizing the target selection logic in getFirestoreConfig. Feedback points out an inconsistency in the single-database configuration path, where global and database-scoped resource selections are not merged, unlike in the multi-database path.

[gemini-code-assist]

In the single database configuration path, the code does not combine global and database-scoped resource selections. If selection.allDatabases is true (e.g., due to a global selector like firestore:rules), it directly uses selection.allResources and completely ignores any database-scoped selectors defined in selection.byName.\n\nThis is inconsistent with the multi-database array path below, which correctly merges both global and database-scoped resource selections for each database. This discrepancy was not caught by the tests because fsConfig.spec.ts only tests the array configuration, and prepare.spec.ts stubs getFirestoreConfig to return an array.

      const resources = new Set(selection.allDatabases ? selection.allResources : []);\n      for (const r of selection.byName.get(databaseId) || []) {\n        resources.add(r);\n      }