Use useQuery in place of usePromise for EDA subsetting and visualizations

[bobular]

• refactor data requests
• make sure user db PATCH requests don't keep going forever
• spinner behaviour
• cancel main variable behaviour
• check date histograms work (I saw a date-related runtime exception once when other things weren't working very well either)
• test bad variable behaviour in MapVEu
• barplot
• boxplot
• test mbio
• lineplot
• mosaics
• scatter plot (maybe set cacheTime in useQuery to 60 seconds (in ms) for scatterplot?) - default is 5 minutes
• test mbio scatter behaviour
• other plots (volcano, networks etc) --> Upgrade MBio volcano and network visualizations to use react-query client-side caching. #1265

[dmfalke]

All "MultiFilter" variables appear to be broken. An example can be found with a clinepi-site (using qa.clinepi): http://localhost:8080/a/app/workspace/analyses/DS_841a9f5259/new/variables/PCO_0000024/ENVO_00003064.

[dmfalke]

I think it's because one of the deps is nullish:

web-monorepo/packages/libs/eda/src/lib/core/hooks/cachedPromise.ts

Line 24 in 65004b3

const enabled = queryKey.every((val) => val != null);

[bobular]

Thanks @dmfalke - I have fixed this now.
I did test it but I must have already checked some checkboxes before deploying the useQuery.

[dmfalke]

I started testing with a clinepi site, and ran into an issue with a MultiFilter. See details below.

[dmfalke]

I think it's because one of the deps is nullish:

web-monorepo/packages/libs/eda/src/lib/core/hooks/cachedPromise.ts

Line 24 in 65004b3

const enabled = queryKey.every((val) => val != null);

[bobular]

Hi @dmfalke thank you for the review.
I cleaned up a lot of dependency warnings and the multifilter bug you spotted.

[dmfalke]

I think this all looks good.

At some point, we might want to consider moving QueryClientProvider to a more central place, such as the Root component in wdk-client. However, this raises some questions about how to properly deal with dependencies like this, across packages.