Console: add kmsUnavailable option for S3 catalogs

[yalindogusahin]

Summary

• Adds the kmsUnavailable field (already supported by the Polaris REST API's AwsStorageConfigInfo, added upstream in (feat) Add support for no KMS with s3-compatible backend polaris#3501 and exposed via the CLI's --no-kms flag on catalogs create) to the console's StorageConfigInfo type, the create/edit catalog forms, the details view, and the checked-in OpenAPI spec.
• Lets console users mark an S3 (or S3-compatible: MinIO, Ceph RGW, VAST, etc.) catalog as not supporting KMS, so Polaris skips adding wildcard KMS IAM policy statements when vending scoped credentials.
• Mirrors the existing stsUnavailable/pathStyleAccess boolean field pattern already used in both catalog modals.

Changes

• console/src/types/api.ts: add kmsUnavailable?: boolean to StorageConfigInfo
• console/spec/polaris-management-service.yml: add kmsUnavailable to AwsStorageConfigInfo, matching the upstream Polaris spec wording
• console/src/components/forms/CreateCatalogModal.tsx / EditCatalogModal.tsx: add the s3_kmsUnavailable form field, checkbox UI, and payload wiring
• console/src/pages/CatalogDetails.tsx: display KMS Unavailable: true in the S3 storage config section when set

Test plan

• npm run lint passes with no warnings/errors
• npx tsc -b --noEmit passes with no errors
• Manual click-through in a running console against a live Polaris backend