Changelog for MCP changes and latest FDC emulator (#9244)

Author: joehan

CHANGELOG.md

@@ -1,5 +1,10 @@
 - Fixed an issue with deploying indexes to Firestore Enterprise edition databases where explicit `__name__` fields could be incorrectly handled.
-- The `experimental:mcp` command has been renamed to `mcp`. The old name is now an alias.
+- Graduated the MCP server from experiemental, and renamed the `experimental:mcp` command to `mcp`. The old name is now an alias.
+- Consolidated some MCP tools to reduce the total number presented to LLMs.
+- Renamed some MCP tools for clarity.
+- Renamed the `deploy` MCP prompt to `firebase_deploy` for consistency.
+- Added a `firebase_read_resources` MCP tool which can be used by LLMs to fetch guides or docs via `firebase://` links.
+- Added a new `/firebase:init` MCP prompt which can guide you through setting up backend services or Firebase AI logic for your app.
 - `firebase_update_environment` MCP tool supports accepting Gemini in Firebase Terms of Service.
 - Fixed a bug when `firebase init dataconnect` failed to create a React app when launched from VS Code extension (#9171).
 - Added seed_data.gql to Data Connect's initial movie template (#9232).
@@ -8,3 +13,8 @@
 - Improved the clarity of the `firebase apptesting:execute` command when you have zero or multiple apps.
 - Fixed an issue where `firebase deploy --only firestore` would fail with 403 errors on projects that never had a database created.
 - Fixed an issue where deploying multiple Hosting sites with Functions could encounter a race condition (#9235).
+- Updated the Data Connect local dev toolkit to 2.14.0, which includes the following changes:
+  - Fixed a bug where @default(value) and @default(expr) is not validated on enum fields.
+  - JS/Kotlin codegen: Issue where if no response type was generated, generation would crash.
+  - Dart codegen: Fixed issue where if field name doesn't match name of enum, compilation breaks
+  - Dart codegen: Override `==` to allow for equality between data classes.