[AWS::RedshiftServerless::Workgroup] - [BUG] - Creation failure when using require_ssl = false

### Name of the resource

AWS::RedshiftServerless::Workgroup

### Resource Name

_No response_

### Issue Description

When creating a Redshift Serverless workgroup initially, we require SSL to be false, HOWEVER we are getting the error mentioned in the `Observed Behaviour` section.

### Expected Behavior

SSL is Disabled upon a Redshift workgroup creation. This can be achieved internally within CloudFormation by:

1. Creating the Redshift workgroup
2. Updating it to include require_ssl false

### Observed Behavior

> Resource handler returned message: "You can't disable require_ssl while the workgroup is being created. To disable require_ssl, update the workgroup after creation. (Service: RedshiftServerless, Status Code: 400, Request ID: b25f2a01-3c75-4003-a3a7-ccdbef3736a8) (SDK Attempt Count: 1)" (RequestToken: 179aed8e-19cd-6080-10c6-65c0e9c076d5, HandlerErrorCode: InvalidRequest)

### Test Cases

Done via the CDK

```
this.redshiftworkgroup = new redshiftserverless.CfnWorkgroup(
this,
'RedshiftWorkgroup',
{
workgroupName: props.workgroupName,
namespaceName: cfnNamespace.namespaceName,
subnetIds: this.subnets.map(subnet => subnet.subnetId),
securityGroupIds: [this.securityGroup.securityGroupId],
enhancedVpcRouting: true,
baseCapacity: 8,
configParameters: [
{
parameterKey: 'require_ssl',
parameterValue: 'false',
},
],
}
);
```

### Other Details

_No response_

Start by reproducing the AWS::RedshiftServerless::Workgroup creation through the CDK test case described in the issue, using require_ssl set to false. Review the resource behavior and the reported InvalidRequest response. Done means a workgroup can be created with SSL disabled, either directly or through the described create-then-update sequence.

Written by the indexing model from the issue text.