feat: uses autoscaler module instead of repeating code

[jubranNassar]

Description of the change

This PR removes all the duplicated code from the autoscaler repo and calls it instead

Type of change

• Bug fix (non-breaking change that fixes an issue);
• New feature (non-breaking change that adds functionality);
• Breaking change (fix or feature that would cause existing functionality to not work as expected);
• Documentation (a documentation or example fix not affecting the infrastructure managed by this module);

Checklists

Development

• All necessary variables have been defined, with defaults if applicable;
• The code is formatted properly;

Code review

• The module version is bumped accordingly;
• Spacelift tests are passing;
• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached;
• This pull request is no longer marked as "draft";
• Reviewers have been assigned;
• Changes have been reviewed by at least one other engineer;

[lorengordon]

This creates a unversioned dependency on the autoscaler module. Changes to that repo will be picked up by users of this module without any increment to the version of this module. From one init to the next, suddenly this module may do different things. I really try to avoid that kind of "automatic" implicit dependency update. Can you please at least pin the version in the module block?

Or, better in my opinion, reverse the dependency. The upstream module should invoke this project. This project is the terraform module, and specializes in terraform syntax. The upstream project is just the lambda function code.