If a service has a conflicted config value then we don't allow them to commit their queued changes
config conflicts no longer block comitting the changesets
Added tests for the config conflict details in the deployer bar summary
Merge pull request #599 from hatched/block-confirm-conflict

Conflicted service values cause notification in deployer bar summary

If the user has changed a configuration value and then another one comes in over the delta before they have committed then their config value is in a conflicted state. In the deployer bar summary we now show them the services which have conflicted values and allow them to go resolve the issues.
Added the manual provider to the supported container types list and made it more resilient if it is an unknown provider
Added tests to make sure we have the appropriate providerFeatures values
Add expose/unexpose to the ecs
Add custom user settings UI.

- Adds UI in the keyboard help menu for setting custom GUI settings remembered
through localStorage.
- Adds option for force container support regardless of provider.
- Adds option to set the environmentName regardless of the deployment.
- Adds option to disable the EU cookie notice.
Merge pull request #601 from mitechie/add-config

Add custom user settings UI.

- Adds UI in the keyboard help menu for setting custom GUI settings remembered
through localStorage.
- Adds option for force container support regardless of provider.
- Adds option to set the environmentName regardless of the deployment.
- Adds option to disable the EU cookie notice.
Merge pull request #602 from hatched/manual-provider-1376353

Fixes container header rendering bug #1376353

When running on the manual provider we didn't have a proper `providerFeatures` property so it didn't render the container header. This adds the manual provider to the list and creates a more resilient fallback for future unsupported providers.
Merge pull request #603 from makyo/ecs-expose

Add expose/unexpose to the ecs