Fix SQS and SNS module bugs

Gave SQS queues and SNS topics separate KMS keys (#252)

This way we can give roles/users decrypt/encrypt access just for those keys instead of for the root one of the account we use for the top security stuff.

Cloud agnostic

Made opta cloud-agnostic (#241)

* Made opta cloud-agnostic

* debug

* Test fixing

* debugging

* debugging

Bug fixes

v0.13.3

Added dependency update option for helm

Bug fixes

v0.13.2

bugfix

Bugfix

• Cosmetic bugfix

IAM support

• Support IAM users/roles
• "did you mean" for the cli commands
• Ability to opt out of datadog/sentry/amplitude tracking

Ignore changes to kms

• Fixes a bug where EKS might get recreated if it thinks there is a change to kms

Enable GRPC

GRPC support (#229)

* wip

* bugfix

* wip

* wip

* wip

* Ignore subnet changes and enfore provider versions

* test fixing

* Debugging

* debugging

* Fixing tests

Helm chart support!

helm chart support (#225)

* helm chart support

* Bugfixing

RunX module!

Improved opta ui module (#223)

* Improved opta ui module

1. The service must inherit from the environment always. (sort of-- there is nothing stopping someone from redundantly adding the runx module in the service, but it changes nothing)
2. For the environment, they should only ever need to save the api key once. It should not be required as an envar everytime (stored in AWS parameter store or google secret manager)
3. The service must be able to fetch the stored secret containing the api key
4. It is ok to treat the runx module special (it is, only 6 lines where we run its process or posthook step in the service runs as well)

* linting

* try

* try

Co-authored-by: Nitin Aggarwal <nitin@runx.dev>
Co-authored-by: Nitin Aggarwal <nitin.agg1909@gmail.com>