[AWS::EC2::InstanceConnectEndpoint] - [BUG] - ClientToken without apparent purpose in CloudFormation context

### Name of the resource

AWS::EC2::InstanceConnectEndpoint

### Resource Name

AWS::EC2::InstanceConnectEndpoint

### Issue Description

The [resource parameters ](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-ec2-instanceconnectendpoint.html)include ClientToken with the description `Unique, case-sensitive identifier that you provide to ensure the idempotency of the request.`

I think this does not make sense in the CloudFormation context and is just a copied over remnant from the [CreateInstanceConnectEndpoint API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateInstanceConnectEndpoint.html). For the API it makes sense to be idempotent, but not for the deployment model of Cloudformation.
If it serves no purpose, it should be removed.

### Expected Behavior

ClientToken having a purpose or not be a parameter.

### Observed Behavior

ClientToken being a parameter without apparent purpose.

### Test Cases

documented resource parameters

### Other Details

_No response_

Start with the documented AWS::EC2::InstanceConnectEndpoint parameters and compare ClientToken with the CreateInstanceConnectEndpoint API documentation linked in the issue. Verify whether CloudFormation uses the token for idempotency; done means documenting its purpose or confirming that the parameter should be removed.

Written by the indexing model from the issue text.