used to get capability request data for the status page
- Added new subcomponent area, where a `capability-request` component
  has been added; will be where the status page is developed; added
  route for it
- Added a component breakdown for the CReq status page (`components.md`)

`create_capability_request` (ex: `capability/null/request/1/submit` is
now `capability/request/1/submit`)

deprecated); added Prettier code formatter

WS-195, WS-76: Notification System now working and sending emails on request submission and completion

 - New DestinationTempFile for writing tempfiles into the destination which eventually get added
 - All of the close() methods are now streaming
 - Implemented ChecksumDecorator
 - Implemented FetchFile decorator

 - New DestinationTempFile for writing tempfiles into the destination which eventually get added
 - All of the close() methods are now streaming
 - Implemented ChecksumDecorator
 - Implemented FetchFile decorator

* refactored LocationReport accepts a List[str] rather than a namespace
* created stand-in for archive service so that tests won't hit the real one

- made our volume mounts dynamic with ENV variable
- changed our test deployment trigger with git tags as end-of-sprint-[0-9]+

that clicking the buttons creates corresponding requests and executions

This reverts commit 08dbc452.

* refactored LocationReport accepts a List[str] rather than a namespace
* created stand-in for archive service so that tests won't hit the real one

changing default spl to smaller image spl

Changed workflow temp location from `$(HOME)/workspaces_tmp` (`/root/workspaces_tmp` in the container) to `/tmp/workspaces_tmp`

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

Added the ability to compare capability executions by their creation timestamp; made it so encountering exceptions when receiving messages does not block the system