Add API key migration wizard support

[premtsd-code]

Summary

Stacks on #3043. Adds api-key as its own top-level resource group in the migration wizard, parallel to platforms.

Backend uses the kebab-case 'api-key' resource id (matches Resource::TYPE_API_KEY in utopia-php/migration). The form field name apiKeys stays camelCase as it's a local property.

Cross-repo

• Add API key migration support utopia-php/migration#183
• Add API key migration support appwrite#12308
• appwrite-labs/cloud#4032

[greptile-apps]

Greptile Summary

This PR extends the migration wizard's integrations resource group to support API keys alongside platforms, wiring up the 'api-key' backend resource type through the store, form-to-resource mappings, and the report UI.

• migration.ts: Adds ApiKey: 'api-key' to MigrationResources, an apiKeys sub-field under initialFormData.integrations, the friendly label entry, and the Appwrite provider resource list; updates both migrationFormToResources and resourcesToMigrationForm to handle the new field.
• resource-form.svelte: Expands the shouldRenderGroup('integrations') check to also test for ApiKey availability; getReportKey is unchanged so the badge still reflects only the platform count.
• importReport.svelte: Adds apiKeys label and description strings to the two display maps consumed by the accordion component.

Confidence Score: 5/5

Safe to merge; changes are additive and tightly scoped to the integrations resource group with no impact on other migration paths.

All three files receive small, targeted additions that follow the existing patterns. The round-trip between migrationFormToResources and resourcesToMigrationForm is correct for the one exercised code path (selectAll with a full provider resource list). The only gaps are a display-only badge count that misses API keys and a theoretical drift in resourcesToMigrationForm that cannot be triggered through the current UI.

No files require special attention for merging.

Important Files Changed

Filename	Overview
src/lib/stores/migration.ts	Adds 'api-key' resource type, ApiKey to MigrationResources/ResourcesFriendly/providerResources, and apiKeys sub-field under integrations; round-trip symmetry between migrationFormToResources and resourcesToMigrationForm is correct for current usage but has a theoretical one-way drift when ApiKey is present without Platform.
src/routes/(console)/(migration-wizard)/resource-form.svelte	shouldRenderGroup for integrations correctly checks both Platform and ApiKey, but getReportKey still maps integrations to 'platform' only, so the accordion badge won't reflect API key counts.
src/routes/(console)/project-[region]-[project]/settings/migrations/(import)/importReport.svelte	Adds apiKeys label and description entries to labelMap and descriptionMap for the integrations group; changes are straightforward and consistent with existing patterns.

_{Reviews (2): Last reviewed commit: "Add API key migration wizard support" | Re-trigger Greptile}