Let users set QC status for multiple samples from /groups

[alkc]

This update adds a dropdown menu to /groups allowing users to toggle QC status for multiple samples.

The QC form is submitted to new route groups.qc_status which updates the QC status for the selected samples and redirects back to /groups.

The sample selection in the sample JS table is retained on page reload through GET args. This is implemented with the assumption that the end-user won't try to set the QC status for so many samples at the same time that the GET request grows too long.

Other changes:

• Added route groups.qc_status
• Added Enum for QC statuses
• Added option to /groups view to render the page with pre-selected samples in the JS table using GET args.
• Changed whitespace control to jinja to trim whitespace left behind by in-line template code

Closes #97

Suggested test sequence:

1. Setup new bonsai instance from this branch and throw a few samples at it
2. Go to /groups and verify that the QC button is disabled
3. Select a few samples and verify that the QC controls can be accessed
4. Setting QC to passed results in a page reload and a change in the QC status of the samples
5. Setting QC to failed results in a page reload and a change in the QC status of the samples. The correct follow-up action and comment is added to the affected samples.

TODO:

• [ ] Review current changes
• [ ] Update CHANGELOG
• [ ] Make QC dropdown menu wider
• [ ] Organize new JS code better in new templates?
• [x] Fix merge conflicts

[alkc]

I've deduplicated all the QC form code back into sample/sidebar.html. Could be moved to some non-blueprint specific template dir, but I'm saving that for some future update.

the /samples sidebar and /groups QC form now use the same macros for both the HTML and JS enhancements.

Demo of QC in /groups:

Demo of QC in /samples

[alkc]

I've rebased the branch onto master (hopefully w/o breaking anything), incorporated the suggested fixes and deduplicated the QC form templates/macros.

See above for updated demos.