optionally remove deadletter alarm

[mapsam]

This adds a deadletterAlarm option to provide a way to bypass creating the deadletter queue alarm resource. Resolves #287

Tests: wasn't sure how to properly test since there's only a single template snapshot. Is it worth creating a second snapshot without the alarm resource?

cc @mapbox/platform

[vsmart]

LGTM 💯

[mapsam]

Thanks @vsmart! Going to do a dev release to test out first, and will report back.

[mapsam]

Confirmed that template diffs no longer include the alarm resource!

---------------------------------------------

       },
       "Type": "AWS::CloudWatch::Dashboard"
     },
-    "WatchbotDeadLetterAlarm": {
-      "Properties": {
-        "AlarmActions": [
-          {
-            "Ref": "WatchbotNotificationTopic"
-          }
-        ],
-        "AlarmDescription": "Provides notification when messages are visible in the dead letter queue",
-        "AlarmName": {
-          "Fn::Join": [
-            "-",
-            [
-              {
-                "Ref": "AWS::StackName"
-              },
-              "Watchbot-dead-letter"
-            ]
-          ]
-        },
-        "ComparisonOperator": "GreaterThanOrEqualToThreshold",
-        "Dimensions": [
-          {
-            "Name": "QueueName",
-            "Value": {
-              "Fn::GetAtt": [
-                "WatchbotDeadLetterQueue",
-                "QueueName"
-              ]
-            }
-          }
-        ],
-        "EvaluationPeriods": 1,
-        "MetricName": "ApproximateNumberOfMessagesVisible",
-        "Namespace": "AWS/SQS",
-        "Period": "60",
-        "Statistic": "Minimum",
-        "Threshold": 1
-      },
-      "Type": "AWS::CloudWatch::Alarm"
-    },
     "WatchbotDeadLetterQueue": {
       "Description": "List of messages that failed to process 14 times",
       "Properties": {

---------------------------------------------

Merging and releasing as 4.12.0 🎉