fix(aws): Fix IPv6 addresses being incorrectly associated when cloning server groups that have launch templates enabled (#6979) (backport #10142)

[mergify]

This is a fix for #6979.

The IPv6 checkbox was previously checked when it should not have been.

This line:

associateIPv6Address: shouldAutoEnableIPv6 || Boolean(ipv6AddressCount),

Was casting the entire object below to Boolean, which ALWAYS resulted in a value of true:

[
  {
    "deviceIndex": 0,
    "groups": [
      "sg-0a1a8a45acf3192b8"
    ],
    "ipv4Prefixes": [],
    "ipv6AddressCount": 0,
    "ipv6Addresses": [],
    "ipv6Prefixes": [],
    "privateIpAddresses": []
  }
]

The change casts the value of ipv6AddressCount within the object to Boolean instead of the object itself.

---

This is an automatic backport of pull request #10142 done by Mergify.