1. Removed the "success = true" and "success = false" in response messages as the client will rely on HTTP code to be informed of success/failure.
2. Changed the error object to be an array of errors.
3. Reformatted the errors in the spec to be just a status code followed by a message instead of showing their JSON representation.

Apart from that I think there is some value in having possible errors after each endpoints, rather than having them grouped together at the top. This way, the client implementer doesn't have to look at all the errors in sequence to decide whether the relevant endpoint does or doesn't include which errors.

@nopara73 @dangershony @dev0tion any thoughts?

Added support for VS2017

- Added login component
- Use temporary navigation (based on success parameter in the body)
Todo: use HTTP Status

Added some API endpoints

Fixed Load controller method

- Added transaction history
- Added unused receive addresses list
- Added balance component in menu

- Upgrade Angular
- Use JSON-Server to provide mock API data
- Add wallet status call

* The full is now able to notify the wallet with new blocks
Provided a temporary endpoint for demo purposes

* Updated to "Stratis.Bitcoin": "1.0.1.3-alpha"

* Update global.json

Fix tests
- Fixed Unit (Karma) tests
- Fixed End2End (Protractor) tests

Add Webpack to cleanly access Electron API

- Cleaned up Electron files
- Added webpack to target electron-renderer
- Clean way of accessing the Electron API within Angular

Move UI to root directory

Finish API endpoint specification 

# Conflicts:
#	Breeze.Documentation/ApiSpecification.md

Add Breeze.UI