Add a dataset browser

[skearnes]

Along with some significant UI reworks 😄

To test, you'll need to rebuild the test database to include the new datasets table, and use it when you launch:

$ cd ord_interface
$ ./build_test_database.sh
$ docker build --file Dockerfile -t openreactiondatabase/ord-interface .. && docker compose up

Partially addresses #35

[ipendlet]

Overall I think that this is a step in the right direction and will significantly improve the usability of the website. The interface is far more intuitive and clean than the previous version.

I have reviewed and manually tested the following interactions and they performed acceptably on the local instance:

• [ ] Interacting with the reaction schemes, urls, and reaction tables
• [ ] Viewing and interacting with the UI for a specific reaction

Bugs:

• [x] When executing a substructure search the UI returns you back to the dataset selection screen. Could not test through UI
• [x] Reaction search returns back to dataset selection screen. Could not test through UI. Likely search button redirect needs to be adjusted.
• [x] Contribute button on development server redirects to the webUI instead of to the local instance

Some suggestions for aesthetic changes (happy to help with these through creating issues and following up with PRs where I can):

• [ ] Instead of Reagents and Reactions have two separate buttons having a single ‘search’ button + a ‘filters’ button would be nice.
  • [ ] Search would be for reagents or reactions (you only should allow one at a time)
  • [ ] Filters could be for things like yield, date, etc.
• [ ] Faceted filtering functionality. Filter reactions across all datasets by type, yield, author, date range, reaction scale, mode of the reaction (high throughput, singleton)
• [ ] Enable search to target specific portions of the reaction (or even the whole reaction substructure search — do this through piecewise comparison combined with maximum scaffold similarity)
• [ ] Count of unique reactant combinations, and unique condition sets should be displayed in the dataset browser
  • Helps to answer: What am I getting with this particular dataset?
• [ ] Yield/conversion, reaction name, and a check list overview the thoroughness of the entry should be included on the search table (I.e., does the entry include things like conditions, details about agents, associated procedure as text / details / both).
• [ ] Give the user the ability to select multiple reactions and export a dataset from the list
• [ ] Some of the tables in the UI are small and have tabs. These tabs could be positioned next to each other unless the exceed the width of the screen to display content simultaneously.
• [ ] Links to pubmed or chemspider record of the products of the reaction would be a plus

[skearnes]

Thanks @ipendlet; I'll fix the bugs you mentioned and then I'd like to merge (after #40 is in). Then we can address your other comments in future PRs---does that work for you?