Amazon Data Firehose to deliver data from an MSK cluster to AWS S3 Tables

### Name of the resource

AWS::MSK::Cluster

### Resource name

_No response_

### Description

The AWS Console provides a smooth setup process for connecting Amazon MSK clusters to S3 Tables using Kinesis Data Firehose. However, this same configuration is not yet fully supported when using CloudFormation.

Issue 1: Catalog ARN Format Mismatch
- CloudFormation Requirement: CatalogArn must follow format arn:aws:glue:region:account-id:catalog
- Expected Behavior: Should reference S3 Tables catalog (managed by Lake Formation)
- Observation: The catalog appears in Lake Formation, not in AWS Glue
- Problem: CloudFormation validation rejects non-Glue catalog ARNs

Issue 2: Unnecessary Warehouse Location
- CloudFormation Property: WarehouseLocation in CatalogConfiguration
- Issue: This appears required for self-managed Iceberg tables in standard S3 buckets
- Question: Should this be omitted for managed S3 Tables, or what value should be specified?

Issue 3: S3Configuration Purpose
- Question: Is the S3Configuration section intended for error records and backup data storage?
- Concern: Unclear if this should reference the same table bucket or a separate standard S3 bucket

### Other Details

_No response_

Start with the three configuration questions in the issue: CatalogArn, WarehouseLocation, and S3Configuration for an MSK-to-S3 Tables delivery through CloudFormation. Compare the CloudFormation resource behavior with the AWS Console setup and determine the supported values and expected managed-table configuration; done means each ambiguity has a documented, actionable resolution.

Written by the indexing model from the issue text.