Combine awsemfexporter and awscloudwatchlogsexporter

[aateeqi]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Currently, the awscloudwatchlogsexporter lacks some core functionality such as automatically creating log/group stream in cloudwatch.
Based on
#4714
#4721

there's a demand for enhancing functionality for awscloudwatchlogsexporter.

Describe the solution you'd like

This can be done by incrementally combining awsemfexporter and awscloudwatchlogsexporter into the awscloudwatchexporter. Not only will it enhance the logsexporter, but also would create more visibility around the emfexporter's role in pushing metrics to cloudwatch as discussed in #3697.

The following outlines the steps intended to combine the 2 exporters, into 1 exporter (awscloudwatchexporter)

1. Extract the CW logs client from the EMF exporter Extract CWlogs client from EMF exporter and use in Awscloudwatchlogsexporter #6969
2. Use that client in the CW logs exporter Extract CWlogs client from EMF exporter and use in Awscloudwatchlogsexporter #6969
3. Use the extracted version of the client in the EMF exporter
4. Copy the EMF metrics handling to the CW exporter
5. Mark the EMF exporter as deprecated
6. Wait some appropriate period of time and Remove the EMF exporter

Diagram for incremental steps to combine EMF and Cloudwatchlogs exporter

Describe alternatives you've considered

Another solution would involve having the 2 exporters completely independent and using separate clients and pushers. The downside of this would be much reused code and a confusing user experience that involves 2 exporters to cloudwatch

Additional context
Add any other context or screenshots about the feature request here.

[anuraaga]

I think the title is something like "Share logs pushing logic between emf and logs exporter". Combining would leave us with only one exporter component, which is not the goal

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.