kill the cloudwatch_monitoring module

[ryandeivert]

Background

The cloudwatch_monitoring module is absolute 🗑️. Right now there is a janky dependency between the kinesis module and this one and it's easy to mess up. Also, the configuration for alarm settings is terrible and requires a user to properly set unwieldy strings like kinesis_iterator_age_error_evaluation_periods (??? whyy). Our lambda module already supports configuring alarms, with a pleasant way of configuring settings. The kinesis module should do the same, and the cloudwatch_monitoring module should die.

Desired Change

Deprecate the cloudwatch_monitoring module in favor of applying alarms within other modules directly. The source of the cloudwatch_monitoring module can be repurposed for this, but the module of cloudwatch_monitoring itself should never be explicitly used going forward.