BLAST redesign

[childers]

1. Legacy blast is a very clean and stable interface that also works well on smaller screens. (General display)
2. Vigilance on simple mouse-overs without clicking seems to be necessary to ensure that I continue to select the intended organism in setting up a blast query. (Submission page)
3. When working on complicated genes, which require iterative blasting or blasting for specific exons or motifs individually, the back browser functionality of the legacy system recalls the species and the type of blast (e.g., tblastn) automatically, which saves time and worry. (Going from results back to submission and keeping some settings see add jbrowse integration back as a option in settings.py #119 (closed))
4. Also, there never seems to be smooth scrolling navigability within the blast search results subwindows, and where results always require up-down and left-right scrolling. (Results page)
5. I repeatedly struggle to select the results I want to view and to ensure that I'm actually at the top of the blast hits and haven't inadvertently scrolled down without noticing. (results page)

[hsiaoyi0504]

When designing new BLAST page, I recommend to consider using modern front-end js library rather than JQuery like ReactJS, Vue.js, AngularJS.

[mpoelchau]

Other examples of BLAST interfaces:

• https://www.sequenceserver.com/ (http://hymenopteragenome.org/hgd_blast/)
• Tripal Blast: https://www.hardwoodgenomics.org/blast

[r06942072]

For the point 3, I make a new issue #273

[r06942072]

For query page(Submission page), see #277