v2.1.0 - Upgrade compatibility

Full Changelog: v2.0.0...v2.1.0

I upgraded my own Foundry install from v11 to v12, and made a few changes as a result from learnings. Mainly, making some names a bit looser so that AWS can successfully deploy two stacks side-by-side.

• Changed the security group to be based on the stack name
• Changed the server name to be based on the stack name
• Less restrictive IAM Admin Username
• Improved documentation for upgrading

v2.0.0 - Config rework

• Reworks config to YAML and tidies things up
• Fixes Node install and lint errors - thanks @samdammers!
• Fixes some install issues with Google Drive
• Fixes some update issues with nginx
• Instances reduced for simplicity and given Foundry generally works just fine on a t4g.small for most use cases
• See the changelog for full notes

v1.2.0 - IPv6 and some fixes

• Adds initial IPv6 work
• Fixes some issues with the install script
• A few tidies

v1.1.0 - Tidying and Linux Security Patching

• Harmonise shell brackets (this always catches me out)
• Fix AWS IP messaging when using Foundry on a primary domain
• Add some extra protection around invalid file sizes (if HTML is returned as in a 404 or 5xx server error)
• Enable AWS Linux security auto-updates by default
  • Also added a utility script to enable, disable or run updates as you may wish
• Tidy comments and add numbers to each section to help with noting how far the script gets
• Add some extra comments to files to help indicate their usage

v1.0.0 - Initial Rework

• Foundry 11 support
• Amazon Linux 2023 and newer instance types
• Node 20.x
• Various fixes and updates to support AWS and Foundry changes