Gke 1.27 (#118)

EKS Module version change (#117)

EKS Upgrade + Subnet changes (#115)

TFBulkChanges (#113)

* Provider changes

* Elasticache, EKS, Redis provider block fix

* Elasticsearch, elasticache module provider fix

* MSK Provider

* Aurora postgresql enhancements

* Removed mariadb 10.3 from schema

* Removed mariadb 10.3 from schema

* Elasticsearch redis 7 + aurora serverless directory change + document db versions

* MariaDB sort order

* Allow major engine version upgrades

* Allow major engine version upgrades to rds

* Allow Aurora verison upgrade

S3 Bucket ACL Error Fix (#111)

* S3 Bucket ACL Error Fix

* Provider Version

fix: vpc creation fails because of unexpected variables (#110)

VPC creates are failing my guess is that the required provider blocks in the upstream module which is

```terraform
terraform {
  required_version = ">= 0.13.1"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 3.63"
    }
  }
}
```
is picking up the latest provider version upstream (`5.x.x`). This is causing issues (my guess is move from 4 to 5 had breaking changes). We should be more pessimistic about version upgrades. I changed it to `4.67.x` (only patches will be allowed). `4.67` is the latest in the `4` series and it is working for us. I can't change it to `3.64.x` because downgrading might not be backwards compatible.

Similar issue might happen with other modules as well, so we need to pin their version as well.

Merge pull request #109 from argonautdev/cluster_autoscaler_1.27_changes

Adding missing permissions to cluster autoscaler

Merge pull request #108 from argonautdev/gke_spot

Spot support for GKE Nodepool

Merge pull request #105 from argonautdev/rds_snapshot

RDS restore snapshot changes

Merge pull request #99 from argonautdev/rds-mariadb

MariaDB