fix: Change cloudwatch log group output to include all created log groups

[ottramst]

Description

Change the Cloudwatch log group outputs to include all created log groups information

Motivation and Context

When using a configuration such as:

module "elasticache" {
  ...
    log_delivery_configuration = {
    engine-log = {
      destination_type                       = "cloudwatch-logs"
      log_format                             = "json"
      cloudwatch_log_group_retention_in_days = 7
      cloudwatch_log_group_kms_key_id        = module.kms_elasticache_logs.key_arn
    }
  }
  ...
}

the outputs of cloudwatch_log_group_name and cloudwatch_log_group_arn were null

Breaking Changes

None.

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

[ottramst]

Can I get a pair of eyes on this please?

[bryantbiggs]

this is a breaking change - and one we should probably make at some point. however, why is this needed right now?

[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

[ottramst]

I think it's needed because right now there is no way to get information from the module about operations regarding the Cloudwatch log groups.

If using the configuration provided in the initial message of the pull request, the specified outputs are null

[antonbabenko]

This PR is included in version 1.4.1 🎉

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