Adds custom deployment config support.

[rodrigosalvatoreradix]

Proposed changes

Currently the plugin does not support custom CodeDeploy deployment configuration.
This implementation creates a new customType property that when set to true, is does not adds de prefix CodeDeployDefault.Lambda prefix to the deployment configuration name.
This allow user to create their custom configurations in AWS CodeDeploy and reference them.
This implementation is fully retro-compatible since the property is not obligatory and not defining it default to the current behavior of adding the prefix.

This implementation addresses the issue #155

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)

Further comments

This solution was chosen because its fully retro-compatible and amount to the least amount of change to the current code. Just a single optional property that gives a lot of freedom regarding choosing your CodeDeploy deployment config.