Removing the inspector drop target code and fixing the file parsing of the drag over handlers
Merge pull request #141 from hatched/remove-inspector-droptarget

There isn't any QA for this branch.

This takes the drag over handler fixes from PR #136 and adds them here as well.
Set version for release: 1.0
Set version back to unreleased
Added functionality to parse local zip contents to determine if there are any services deployed using the same charm on local charm drop
adding functional tests for the local charm drop service parsing additions
Added a getServicesFromCharmName utility method to the serviceList
model to simplify testing and functionality in service.js
Added more functional tests for the local charm service parsing
Setting the 'showGetJujuButton' back to false on prod'
Merge pull request #143 from hatched/fix-get-juju-button

This was causing CI to fail.
Merge pull request #142 from hatched/parse-deployed-local

When we drag and drop a local charm it will now check to see if there are any existing services deployed with a similar charm so that it can (eventually) ask the user if they would like to upgrade an existing charm or deploy a new one.

__To QA__
- Drag, drop, and deploy a local charm from your desktop (sandbox works fine)
- Place a breakpoint in service.js:_showUpgradeOrNewInspector()
- DDD the same charm, it should hit your breakpoint.

refresh

- DDD any service that's NOT your local charm
- Place a breakpoint in service.js:_showUpgradeOrNewInspector()
- DDD your local charm and it should not hit the breakpoint
Add CI step to release process
Merge pull request #144 from mitechie/add-ci-process