REST API gives out and parse that into the CapabilityRequest object

`CapabilityService.create_request` instead of duplicating that logic
within the view; changed tests and mocks to go along with the changes

fix CapabilityEngine to actually load the capability execution it's executing and then properly release the engine after completion

forgot to add in the previous MR

Added two new Pyramid views, the first of the capability request views: `view_capability_request` and `create_capability_request`

updated coveragerc config files to reflect changes to the shared packages location and modified run-tests.sh

installs all requirements required by all 3 services; new rule: make
clean, which cleans up your Python environment and your Docker environment; make test now runs setup.py files for all packages

added views directory that will hold logic for views

launches the download capability; moved the capability launching
functionality from the on-click methods to a new method that gets called
by the on click methods

Daniel Lyons authored 4 years ago and Daniel Lyons committed 4 years ago

Separate architecture from readme in delivery

AKA please don't give me heart failure again

Also removed a few unused imports and added some padding to the html template for the workspaces component

* This feature branch replaces the one in !53, which broke the build.

Created page with a button that will send an HTTP request to the capability server; does not currently work

TODO: Make it work with the capability service