(aws-autoscaling): initOptions don't have a timeout field (unlike the one in aws-ec2)

### Describe the feature

There are two very similar if not to say identical interfaces called ApplyCloudFormationInitOptions one in aws-ec2 another in aws-autoscaling:

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.ApplyCloudFormationInitOptions.html
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_autoscaling.ApplyCloudFormationInitOptions.html

The one in aws-autoscaling doesn't have timeout for some reason and it is very unfortunate.

### Use Case

Use case is using `init` that takes >5 minutes (default timeout), which is not so unusual with Windows instances. I have a mix of EC2 and ASGs in my stack and for EC2s I can specify timeout but not for ASG.

### Proposed Solution

Do the same thing the aws-ec2 code does :-D .

### Other Information

_No response_

### Acknowledgements

- [x] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.33.0

### Environment details (OS name and version, etc.)

MacOS 12.4

Compare the two ApplyCloudFormationInitOptions interfaces linked in the issue, starting with the aws-ec2 implementation and then tracing the aws-autoscaling entry point. Confirm how the timeout is propagated and identify the existing tests for both paths; done means autoscaling accepts and honors the same timeout option as EC2.

Written by the indexing model from the issue text.