feat(ecs): add support for ecs service hook details field

[kg-aws]

Issue # (if applicable)

Closes #.

Reason for this change

Description of changes

Added support for ecs service hook details field. AWS::ECS::Service only accepts JSON object as a string for this field.

Public Doc: https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-deploymentlifecyclehook.html#cfn-ecs-service-deploymentlifecyclehook-hookdetails

Describe any new or updated permissions being added

Description of how you validated changes

• Added unit tests
• Updated integration tests

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[aemada-aws]

PR title start with feat(ecs) since you are adding a new feature. it will also require an integ test

[aemada-aws]

Suggested change

	readonly hookDetails?: any;
	readonly hookDetails?: { [key: string]: any };

then you don't need the validate function, just Fn.toJsonString(hookDetails)

[kg-aws]

So that challenge is CFN only accepts JSON object as string for this field while Fn.toJsonString can convert any primitive datatype or JSON array to string which we need to guard against in CFN.

[aemada-aws]

If you type it as an object, which is the suggested code change, then you won’t need to validate if it is an object.

[kg-aws]

If we limit it to just an object, can we edit to type any in the future in CDK in case CFN implementation supports primitive types as JSON string?

[aemada-aws]

yes

Pull request has been modified.

[kg-aws]

PR title start with feat(ecs) since you are adding a new feature. it will also require an integ test

Fixed the title and I have updated an existing ecs B/G integ-test with HookDetails field.