[aws-for-fluent-bit] cloudWatchLog Opt In

Hi,

Noticed when upgrading from 0.1.21 to 0.1.28 that during 0.1.24 cloudWatch was disabled by default and cloudWatchLogs was enabled.

The projects versioning looks like a typical SemVar approach so I wasn't expecting any issues with this bump but encountered the default config for cloudWatchLogs and an excess of failed transformation mapping logs. Just wanted to highlight that an opt in approach for cloudWatchLogs (and future C implementations) might have a smoother upgrade path, or just a bump to 0.2.X.

Thanks

No files, tests, or entry points are named. Start by comparing the 0.1.21, 0.1.24, and 0.1.28 defaults for cloudWatch and cloudWatchLogs; done means an agreed upgrade-safe opt-in behavior or versioning decision, with the failed transformation mappings addressed.

Written by the indexing model from the issue text.