Initial front-end restructure and code re-design

[MaybeJustJames]

This branch begins a large-scale move of the app to redux and redux sagas for state management. It also restructures the app in a way I think is easier to navigate and think about.

Cleanup

• Webpack config based on this.
• Remove unnecessary/unused build machinery and unused files.
• Remove Google Analytics integration
• Dynamically generate artifact and use default WebPack output directory
• Update most dependencies, removed unused or unnecessary dependincies
• Add a script to visualise the size of the compiled build artifact (bundle-size-analyse)
• Use ts-loader rather than babel to compile ts/tsx (type-checking)
• Upgrade to webpack 5
• Remove reliance on polyfilled Node APIs (path and zip)
• Add linting for use of abstract equality and block delimiters with braces
• Add tests for the front-end using Jest and react-testing-library. Including tests for fetch() And GProfiler previously introduced.
• Use jest-css-modules-transform to handle imports for CSS. Version is intentionally pinned as "4.0.2" breaks tests.
• Wrap the old API in a scary LegacyAPI name
• Extract some of the complexity in the App component in new Main and FullPageNotify components.
• Turn on strict TypeScript type checking and fix all type errors.
• Remove as much CSS as possible and simplify DOM structure
• Introduce a TEST_ONLY flag to avoid hard-to-test side-effects from the legacy API while testing.
• Add local CSS imported only by the component that uses it.
• Remove as many uses of Lodash as possible
• Add a utility function zipLists to zip() a list of lists.
• Refactor the UploadModal to be responsive.
• Reduce use of default exports

Code structure and redesign

• Document code style and design decisions in CONTRIBUTING.md
• Change the structure of getFeature() requests and responses
• Add a "filter by type/category" argument to getFeature() requests
• Redisign of FeatureSearchBox components following the guidelines outlines in CONTRIBUTING.md
• LegacyAPI no longer tracks UUID, sessionMode, sidebar visibility, and cookie consent. These have been moved to Redux.
• Wire in Redux to existing components where useful.
• Use immer to update Redux state.
• Add a Result type similar to the backend Result type.

UI

• Viewer component is now responsive and does less work to render data
• Redisign of UI, the whole UI is a little more responsive and more traditionally "single-page".
• Centre the Welcome page and make it scrollable.

Breaking changes and known issues

• Does not keep (removes) the functionality for "locking" related search entries on searches like "batch" and "All clusters" (#447)
• This PR breaks ViewerSidebar "Clustering Controls". Fixing this is out of scope for the PR, this should instead be fixed after @dweemx cleanup of the ViewerSidebar is merged.
• Lasso selections are not "remembered" when switching between tabs.
• The Babel config file is necessary for Jest. It duplicates the webpack config. If you have a solution to remove the duplication please let me know.
• [VISUAL/STYLING] Annotation voting popup does not persist on mouseover (#427)
• Compare tab break when performing a DnD of one of the annotation onto a viewer.
• [VISUAL/STYLING] Styling changes cause text to overlap in many locations (i.e. Loom selection in sidebar) (#428)
• [BREAKING] Getting metadata from a cell section fails (#429)
• [MINOR] Settings in sidebar do not display when selecting a loom, only after selecting a gene or changing loom (#430)
• [BREAKING] Selecting a cluster in the results, always selects the first result by name (#431)
• [BREAKING] Adding annotations fails with python error (#432)
• [MINOR] Annotation labels remain after clearing feature (#433)
• [VISUAL/STYLING] Regulon tab plots done fill screen (#434)
• [MAJOR] Selecting a regulon causes an infinite loop in the backend (#435)
• [BREAKING] Regulon histogram never displays data (#436)
• [MAJOR] Unable to search for clusters by annotation name (#437)
• [MINOR] Permalink button does nothing (#438)
• [MAJOR] Compare tab does not work with more that one annotation per viewer (#439)

[MaybeJustJames]

Add PR summary points to documentation (conribution manual??)

[dweemx]

/!\ I noticed that <- Pevious and Next -> buttons of the cluster controls (right side bar) don't work anymore. They work in the master branch

[MaybeJustJames]

/!\ I noticed that <- Pevious and Next -> buttons of the cluster controls (right side bar) don't work anymore. They work in the master branch

Reproductions steps:

1. Query "Unannotated Cluster 0"
2. Click on "Next ->" button in the right side bar should take you to the next cluster i.e.: "Unannotated Cluster 1"
3. Click on "<- Previous" button in the right side bar should take you to the previous cluster i.e.: "Unannotated Cluster 0"

[MaybeJustJames]

@dweemx wrt an .nvmrc Node 10 is EOL end of this month. I'm fine leaving this out. What about you?

[MaybeJustJames]

@dweemx Can you elaborate on what "switch from loom" means?

[dweemx]

@dweemx wrt an .nvmrc Node 10 is EOL end of this month. I'm fine leaving this out. What about you?

You mean not having a .nvmrc file or just upgrade to use higher Node version ?

[MaybeJustJames]

@dweemx wrt an .nvmrc Node 10 is EOL end of this month. I'm fine leaving this out. What about you?

You mean not having a .nvmrc file or just upgrade to use higher Node version ?

No I mean it's a users fault if they use an EOL node version. So why have an .nvmrc?

[dweemx]

@dweemx wrt an .nvmrc Node 10 is EOL end of this month. I'm fine leaving this out. What about you?

You mean not having a .nvmrc file or just upgrade to use higher Node version ?

No I mean it's a users fault if they use an EOL node version. So why have an .nvmrc?

Because the user will be sure that the software will work with that version of Node.