(ec2): allow --http-proxy and --https-proxy in Cloudformation helper scripts

### Description

[Cloudformation helper scripts](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-helper-scripts-reference.html) such as [`cfn-init`](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-init.html) include options that allow users to set proxies.

```zsh
/opt/aws/bin/cfn-init --https-proxy https://my-proxy.com
```

These options aren't available in [ApplyCloudFormationInitOptions](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_autoscaling.ApplyCloudFormationInitOptions.html)

### Use Case

When operating in locked down networks where proxies are required to reach Cloudformation endpoints, the `--http-proxy` and/or `--https-proxy` options are necessary

### Proposed Solution

In [ApplyCloudFormationInitOptions](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_autoscaling.ApplyCloudFormationInitOptions.html), allow the option for `httpProxy` and `httpsProxy`

### Other information

I have a PR ready

### Acknowledge

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

Start at ApplyCloudFormationInitOptions and trace how its options are passed to the CloudFormation helper scripts. Done means users can supply both httpProxy and httpsProxy and the resulting cfn-init invocation accepts the corresponding proxy options.

Written by the indexing model from the issue text.