fix(ecs-patterns): resolve not being able to create ECS service in integ.alb-ecs-service-command-entry-point (#29333)

### Issue # (if applicable)

part of #29186 (comment)
Closes #<issue number here>.

### Reason for this change

CFN stack gets stuck after `yarn integ` because of not being able to create ECS service.

```
AWS::ECS::Service | CREATE_IN_PROGRESS
```

```
$ aws ecs describe-tasks --cluster aws-ecs-integ-alb-ec2-cmd-entrypoint-Ec2ClusterEE43E89D-zBVKZa6JEBrW --tasks xxxxxxxxxxxxxxx | jq '.tasks[].stopCode'
"EssentialContainerExited"
```


### Description of changes

Change `taskImageOptions` `image`, `command`, `entryPoint` and add security group.
Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html#example_task_definition-webserver



### Description of how you validated changes

Pass integration tests


### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Author: wafuwafu13