Fix destroy environment workflow failure due to missing variable

[gurevichdmitry]

Summary of your changes

The destroy environment workflow currently fails because a required variable is missing.
This PR adds the missing variable and sets it to the correct value to ensure the workflow runs successfully.

[mergify]

This pull request does not have a backport label. Could you fix it @gurevichdmitry? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[uri-weisman]

Can you please explain why this is needed?

[gurevichdmitry]

The CDR stack passes var.windows_elastic_defend_winrm_ingress_cidr into modules/aws/ec2-windows, which rejects an empty string (and 0.0.0.0/0)
Destroy process did not set that env var, so the variable stayed at its default ""
As a result Destroy then failed variable validation (winrm_ingress_cidr must be set…) even though you only wanted to tear resources down.

╷
│ Error: Invalid value for variable
│ 
│   on main.tf line 103, in module "aws_ec2_elastic_defend_windows":
│  103:   winrm_ingress_cidr    = var.windows_elastic_defend_winrm_ingress_cidr
│     ├────────────────
│     │ var.winrm_ingress_cidr is ""
│ 
│ winrm_ingress_cidr must be set to a restrictive CIDR and must not be
│ 0.0.0.0/0, as this would expose WinRM to the public internet.
│ 
│ This was checked by the validation rule at
│ ../modules/aws/ec2-windows/variables.tf:35,3-13.
╵