- Use /wallet/files to see if the user has created a wallet on the default path (instead of /wallet/status)
- Change load function to POST
- Added login and logout functionality
- Enabled wallet loading
- Various small fixes

API specifications changed

- Handling HTTP status codes (temporary catching all statuses)
- Added default unit tests for all components
- Edited wallet load function
- Moved API error handling to components

Added Swagger controller methods comments

- Added recovery component
- Adjusted setup component to choose between recovery or creation
- Updated mock data to reflect API spec
- Updated components to latest API spec
- Small fixes

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