MSK - Ability to create a cluster with VpcConnectivity enabled

### Name of the resource

AWS::MSK::Cluster

### Resource name

_No response_

### Description

Currently [VPC Connectivity](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_msk.CfnCluster.VpcConnectivityProperty.html) exists as a part of the L1 [CfnCluster](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_msk.CfnCluster.html) construct, this L1 constrcut is generated directly from the CloudFormation template and these same properties are available [in the template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-msk-cluster-connectivityinfo.html). However when this resource is deployed there is a 400 error:

`When creating a cluster, all vpcConnectivity auth schemes must be disabled ('enabled' : false). You can enable auth schemes after the cluster is created. (Service: Kafka, Status Code: 400, Request ID: xxxx) 'vpcConnectivity.clientAuthentication'" (RequestToken: xxxx, HandlerErrorCode: InvalidRequest)`

Enabling VPC Connectivity as a secondary action can take hours depending on the size of the cluster. It would be nice to have the ability to create a cluster with VPC Connectivity enabled.

Link to related CDK issue: [26690](https://github.com/aws/aws-cdk/issues/26690)

### Other Details

_No response_

Start with the AWS::MSK::Cluster resource and the documented VpcConnectivity property, then review related CDK issue 26690 for context. Determine whether CloudFormation can apply the requested setting during cluster creation and define done as creating a cluster with VPC Connectivity enabled without the reported 400 error.

Written by the indexing model from the issue text.