AWS::AutoScaling::AutoScalingGroup - UpdatePolicy does not work with AutoScalingGroup Mixed Instance Policy

## 1. AWS::AutoScaling::Group

## 2. Scope of request

AWS:: AutoScaling:: Group::MixedInstancePolicy causes update failures with UpdatePolicy when a server is launched with Weighted Capacity > 1, and using the Resource Signals feature.

## 3. Expected behavior

When updating a stack with a Mixed Instance Policy, if any instance is launched with a weighted capacity > 1, CloudFormation should take this into account when waiting for resource signals.

Feel free to describe other desired and relevant implementation details.

## 4. Suggest specific test cases

1.
- Deploy a stack with 12 m5.large instances using CloudFormation, and a weighted capacity of 1, with an UpdatePolicy that specifies waiting for resource signals.
- Deploy an update to this stack, switching the 12x m5.large to 6x m5.xlarge, with a weighted capacity of 2.
- The stack will fail to update as it expects 12 resource signals to be sent, even though only 6 new servers have been started by the ASG.

## 5. Helpful Links to speed up research and evaluation

## 6. Category (required) - Will help with tagging and be easier to find by other users to +1

1. Compute (EC2, ECS, EKS, Lambda...)

## 7. Any additional context (optional)

Begin with the issue's CloudFormation reproduction: update an AWS::AutoScaling::AutoScalingGroup from 12 m5.large instances with weighted capacity 1 to 6 m5.xlarge instances with weighted capacity 2 and resource-signal waiting enabled. No repository files or tests are named; done means the update succeeds while waiting for the signals corresponding to the instances actually launched.

Written by the indexing model from the issue text.