aws-msk-alpha: support multi-VPC private connectivity

### Describe the feature

As per the announcement: https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-msk-multi-vpc-private-connectivity-cross-account-access/

Amazon Managed Streaming for Apache Kafka (MSK) now offers multi-VPC private connectivity that simplifies connectivity and access to your Amazon MSK clusters from your Apache Kafka clients hosted in any VPC or AWS account.

### Use Case

Customers currently need to manually turn on the Multi-VPC option within the console. Some customers have requirements around doing all actions via Infrastructure as Code.

### Proposed Solution

_No response_

### Other Information

Currently there are some limitations to keep in mind: https://docs.aws.amazon.com/msk/latest/developerguide/aws-access-mult-vpc.html#mvpc-requirements
- Multi-VPC only on Apache Kafka 2.7.1 or higher.
- Unauthenticated clusters can't use multi-VPC private connectivity.
- Doesn’t support the t3.small instance type.
- Isn’t supported across AWS Regions, only on AWS accounts within the same Region.
- Amazon MSK doesn't support multi-VPC private connectivity to Zookeeper nodes.

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.118.0

### Environment details (OS name and version, etc.)

N/A

Start in the aws-msk-alpha module, then read the linked Amazon MSK multi-VPC announcement and the documented limitations. Determine the existing MSK configuration entry point and how the multi-VPC option should be represented for infrastructure as code; done means customers can enable it without using the console while the documented constraints remain respected.

Written by the indexing model from the issue text.