Add Apollo assembly and feature importing status to JBrowse 2 jobs widget

[carolinebridge]

Resolves #234

Dependent on JBrowse core changes: GMOD/jbrowse-components#3951 (merged), changes will be in v2.7.0

summary of changes

• Adds a new ApolloJobModel to update the jobs widget UI where appropriate
• Adds a safeguard to the add assembly UI to prevent a user from uploading an assembly with an existing name (an operation that will always fail and takes some time if the file is large)
• Utilizes the new jobs manager to update the widget UI when a user attempts to upload a new assembly or upload new features for an assembly

[carolinebridge]

👇 tests are failing because WidgetType 'JobsListWidget' not found, which is included in the jbrowse-components PR

[garrettjstevens]

This only works if a single job is running at a time, which we can't guarantee. For example, I started an upload of a larger assembly file, then while it was running uploaded a small file which finished basically immediately. Then, when the larger one tried to update its percentage, the app crashed since the newer job had cleared out the name, etc. in the Apollo jobs manager. Some jobs also might not be uploads, too, so they may be even more likely to run at the same time.

I think the jobs manager needs to either 1) keep track of each submitted job or 2) be stateless, so instead of storing jobs it's a set of utility functions for helping Changes, etc. add info directly to the job status widget. I lean toward option 2.

Also, the abort controller should be tied to the underlying fetch. So for example, in AddAssembly.tsx, there should be a const controller = new AbortController() and then later in the code

const { signal } = controller
const response = await apolloFetchFile(url, {
  method: 'POST',
  body: formData,
  signal,
})

Then when submitting the job, you'll have

jobStatusWidget.addJob({
  name,
  statusMessage,
  progressPct,
  cancelCallback: () => {
    controller.abort()
  },
})

That will be the same controller as was created in AddAssembly.tsx. This way, when someone clicks on the cancel button in the jobs widget, it will abort the fetch.

[garrettjstevens]

After merging main, it looks like the tests aren't passing because the "Features are being added" message that "importFeatures" is looking for does not exist after this change. I tried to update the test, but didn't have any luck. @dariober, would you be able to take a look at this? Instead of checking for the previous message, I think you can now tell features have been added when the "Completed jobs" section has two entries that both say "All operations successful".

[garrettjstevens]

@dariober never mind, I was able to figure out the tests :)