Update AWS VM template to support IPv6, as Amazon is going to start charging for IPv4

[sgryphon]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The vm-aws-typescript template creates a machine (and network) that only supports IPv4, which is a poor example for a modern solution (with ~50% of the world on IPv6). Also, AWS will start charging for public IPv4 addresses soon, so we should avoid unnecessary use of public IPv4.

This template should at least be updated to dual stack IPv6 (requires just a few small changes), and I suggest adding a configuration option for assignPublicIpv4 that can be turned off (this way only the free IPv6 address will be used).

(Actually, I'm not sure if this is a new feature or should be considered a bug -- deploying an IPv4 only server may make it inaccessible to some people, e.g. if they have IPv6 only clients.)

Affected area/feature

This would be a simple update to the existing template.