feat: show all collections and add reload button in sidebar

[EMTumariscal]

Summary

This PR addresses two issues with the Firestore collection list in the sidebar:

1. Incomplete collection list: projects with more than one page of root collections silently truncated the list because listCollectionIds was called without a pageSize and never followed nextPageToken.
2. No way to refresh: when collections changed on the Firestore side (new collection created, one removed, etc.) the user had to fully leave and re-enter the project to see the update.

Changes

Fix: list every root and subcollection via pagination

• Extract the existing listCollectionIds call from googleController.js into a shared helper in recursiveDeleteRest.js that paginates with pageSize: 300 and follows nextPageToken until exhausted.
• Use the helper from getFirestoreCollections, google:getCollections and google:exportCollections. Error responses from the REST API are now surfaced as ipcResult instead of being swallowed.
• Cover the root and subcollection paths with two new tests in recursiveDeleteRest.test.js (multi-page tokens + subcollection URL).

Feature: reload collections from the sidebar

• A small refresh icon button is rendered next to each Firestore database header in SidebarProjectsList (root projects, service-account projects and OAuth accounts).
• The button calls the new onRefreshFirestoreDatabase(project, firestoreDatabaseId) prop when available, falling back to onRefreshCollections(project) for legacy callers. Both paths stop event propagation so expanding or collapsing the tree is not affected.
• Tooltip text is "Refresh collections" so the action is self-explanatory. The icon uses the standard RefreshIcon from @mui/icons-material and inherits the existing hover treatment (secondary text colour that turns primary on hover).

Tidy: deterministic collection ordering in the sidebar

• normalizeCollections now deduplicates by id, guards against non-array and falsy entries, and sorts the resulting list alphabetically. The sidebar shows a stable, predictable order even when the REST response order changes between requests.
• New regression test loadProjects deduplicates and sorts collections alphabetically pins the new behaviour.

Files changed

File	Change
electron/controllers/firestore/recursiveDeleteRest.js	listCollectionIds now paginates with pageSize: 300 and follows nextPageToken; supports both root and subcollection paths.
electron/controllers/firestore/recursiveDeleteRest.test.js	Two new tests covering pagination and the subcollection URL shape.
electron/controllers/googleController.js	All three call sites (getFirestoreCollections, google:getCollections, google:exportCollections) route through listCollectionIds. REST error responses propagate as ipcResult.
src/features/projects/components/ProjectSidebar.tsx	Wires onRefreshCollections / onRefreshFirestoreDatabase through to SidebarProjectsList.
src/features/projects/components/sidebar/SidebarProjectsList.tsx	Renders the refresh icon button next to each Firestore database header in all three project contexts.
src/features/projects/store/projectsSlice.ts	normalizeCollections deduplicates, guards against non-arrays, and sorts alphabetically.
src/features/projects/store/projectsSlice.test.ts	Regression test for dedupe + alphabetical sort.

Behavior

• Projects that previously showed only the first page of collections now show the complete list, with no UI change beyond more entries appearing.
• The reload button hits the same code path as opening the project, so the user sees the latest collection list without restarting the app.
• Collection order in the sidebar is now stable and alphabetical, independent of REST response order.
• No changes to public APIs, no breaking schema changes, and no new dependencies.

Test plan

• pnpm test — 85 tests pass across 10 test files
• pnpm lint — clean
• pnpm typecheck — clean
• Manual: open a project with more than 300 root collections and confirm every collection is listed
• Manual: add a collection in the Firebase console, click the new refresh icon, and verify the new entry appears without leaving the project