Add feature to expose disabling of auto rollback and disabling of alarms

[rufushonour]

Proposed changes

Hey @davidgf

This PR contains some changes to expose the AutoRollbackConfiguration Enabled flag and expose the AlarmConfiguration Enabled flag for configuration by the user.

Why? So that we can programatically disable these two features when running in an CI. Sometimes we may want to avoid running a deployment with a canary deployment at all as we want to push the change out. We want to be able to say 'Ignore the alarms' and 'Ignore the rollback' thus essentially disabling the plugin for that run.

Types of changes

What types of changes does your code introduce to the plugin?
Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)