feat: Added variable for TLS messaging in SQS queue from karpenter submodule

[Puig99]

Description

Added a the bool variable queue_enforce_tls_messages for the karpenter submodule. It enforces the usage of TLS messaging in the SQS queue

Motivation and Context

I, like many of the users of this modules use them in a work environment. This change helps reaching compliance for security requirements in a corporative environment, allowing the SQS policy to only allow TLS messages in the queue

Breaking Changes

This change is not a breaking change, as it only introduces a not required variable, by default set as false.

How Has This Been Tested?

• [ x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
• [ x] I have tested and validated these changes using one or more of the provided examples/* projects
  I deployed the changes on my own deployment of the karpenter submodule. Then tested it by launching a plan on the example folder.
• [ x] I have executed pre-commit run -a on my pull request

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[bryantbiggs]

why is this needed? there isn't anything sensitive in these messages, they are just capturing and forwarding EC2 events

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.