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.