[FEATURE REQUEST] Change autoscaling_group approach in AWS provider in favor of plain VM creation.

[seriva]

Is your feature request related to a problem? Please describe.
Currently for AWS we use autoscaling_groups to create a set of VMs for a given component group. This approach however has several issues as we cant guaranty the order of the VMs when changing/updating the cluster. This in turn causes issues with scaling some of the components in our cluster.

Describe the solution you'd like
We would like to have the same approach as we have in the Azure provider where we create the VMs ourselves.

Also it would be nice to include the use_network_security_groups feature which is currently unimplemented in AWS. In shirt this should disable the use of any network security rules for the VPC and subnets.

Describe alternatives you've considered
None

Additional context
None

---

DoD checklist

• Changelog
  • updated
  • not needed
• COMPONENTS.md
  • updated
  • not needed
• Schema
  • updated
  • not needed
• Backport tasks
  • created
  • not needed
• Documentation
  • added
  • updated
  • not needed
• Feature has automated tests
• Automated tests passed (QA pipelines)
  • apply
  • upgrade
  • backup/restore
• Idempotency tested
• All conversations in PR resolved
• Solution meets requirements and is done according to design doc
• Usage compliant with license

[przemyslavic]

✔️ creating plain VMs on AWS (without autoscaling groups)
✔️ added sorting in inventory (hostnames are created the same as for Azure)
✔️ added support for use_network_security_groups. When set to false, ssh is not allowed.
✔️ added names/tags for resources
✔️ added support for data disks

Upgrades from older clusters are not supported.