Use different visualizers for each job type

[tddough98]

I reworked how the predict page connects with visualizers so that each prediction pipeline can open results with a different site. The key change are

• remove REACT_APP_LABEL_FRONTEND and LABEL_BACKEND in favor of a visualizer endpoint defined in jobData.js
• update the form sent to the visualizer endpoint
  • The spots visualizer expects this updated form, but I'll need to update the expected form for the mesmer visualizer. This will be a quick pull request into https://github.com/vanvalenlab/deepcell-label/pull/243

As I worked on the Predict component, I separated all the components defined in Predict.js into their own file. Some of the changes beyond copying and pasting into new files are:

• remove unused infoText prop from FileUpload and moved the Grid layout from the Predict component into FileUpload
• remove xs={12} from a Grid in ChannelForm (suggested by a compiler warning)
• rename selectJobType prop in JobForm to jobDropdown to make it clearer that the prop is a React element

There's an addition to .eslintrc.yml to make eslint consistent with prettier autoformatting for switch statements.

[tddough98]

Finally got both the mesmer and spots visualizers working! There's a temporary test instance online that we can use to check things out.

As the mesmer visualizer is a year old now, there are some hard coded checks to change the behavior for the mesmer visualizer. I'm hoping to make the polaris, mesmer, and caliban viewers all match the behavior of the polaris viewer, but for now, there are some simple ternary checks in the VisualizeButton component.

[tddough98]

Yes, REACT_APP_LABEL_BACKEND and REACT_APP_LABEL_FRONTEND should no longer appear anywhere in the codebase. This was motivated by

• the merging of the two thanks to cloudfront. Both the frontend and server can be reached through the same endpoint
• the changing endpoint for each jobtype. Mesmer and polaris load and show their results with different endpoints