fix: Enable transit_encryption_enabled for all avialble engines now that Elasticache supports this

[cmanzur]

Description

Support transit_encryption_enabled for all Engines

Motivation and Context

transit_encryption_enabled was disabled by default for Redis Engine.

Resolves #55

Breaking Changes

No

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[antonbabenko]

This PR is included in version 1.10.1 🎉

[manelpb]

This was supposed to be released as a breaking change. As soon the module version was updated, clusters were trying to be recreated because of this default variable.

      ~ transit_encryption_enabled   = false -> true # forces replacement

cc @bryantbiggs @antonbabenko

[bryantbiggs]

apologies for that - the removal of the prior restriction appears to clash with the current default behavior of the module to enforce encryption

we'll revert for now in #57 and save this change for an upcoming breaking change that will be released under a new major version number

[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.