bump aws provider version to fix conflict

[pnadolny13]

@kgpayne @aaronsteers I can't init the module because of conflicting version constraints:

╷
│ Error: Failed to query available provider packages
│ 
│ Could not retrieve the list of available versions for provider hashicorp/aws: locked provider registry.terraform.io/hashicorp/aws 3.73.0 does not match configured
│ version constraint >= 2.49.0, >= 3.0.0, >= 3.1.0, >= 3.13.0, >= 3.40.0, >= 3.56.0, >= 3.59.0, 3.65.0, >= 3.73.0, < 4.0.0; must use terraform init -upgrade to allow
│ selection of new versions

The squared module references the v0.1.0 release and main has a bunch of name changes that we dont want to apply to squared right now. Could we create a new patch release to fix this?

Additionally it looks like the db versions were auto upgraded so when running an apply I get warnings that it cant downgrade my db from 13.7 to 13.4. This feels like the wrong place to do it since its specific to my deployment but wanted to see what you thought.

[magreenbaum]

@pnadolny13 we can use >= constraint on versions within re-usable modules to prevent conflict errors also in the future.

Regarding db engine version, using a variable might be a good option here. We can set the default to 13.4 then you could pass your version in as a parameter in the workspace where you're calling the module from.