aws-gamelift-alpha: minSize and maxSize don't work

### Describe the bug

Setting `minSize` and `maxSize` on `BuildFleet` don't seem to take effect. Example:

```
const fleet = new gamelift.BuildFleet(this, "Game server fleet", {
fleetName: id,
content: build,
instanceType: ec2.InstanceType.of(
ec2.InstanceClass.R5,
ec2.InstanceSize.LARGE
),
desiredCapacity: 1,
minSize: 1,
maxSize: 2,
runtimeConfiguration: {
serverProcesses: [
{
launchPath: "/local/game/GameServer",
concurrentExecutions: 4,
},
],
},
});
```

When deployed, they don't take effect when viewed in the console:


### Expected Behavior

`minSize` and `maxSize` should work.

### Current Behavior

`minSize` and `maxSize` don't effect anything when deployed.

### Reproduction Steps

See example above.

### Possible Solution

_No response_

### Additional Information/Context

_No response_

### CDK CLI Version

2.101.1

### Framework Version

_No response_

### Node.js Version

v20.8.1

### OS

Ubuntu (WSL2 on Windows 11)

### Language

TypeScript

### Language Version

5.2.2

### Other information

_No response_

Start at the BuildFleet construct and reproduce the example with CDK CLI 2.101.1, then inspect the synthesized GameLift fleet configuration for minSize and maxSize. Done means the deployed fleet reflects minSize 1 and maxSize 2 in the console.

Written by the indexing model from the issue text.