Item blocks message always shows the limit as 1, even if it is 2, 3, 4, etc.

Parent issue to track a bunch of migration and deprecation tasks – with QA regression testing.

useBatchedFetch is using the react-query useInfiniteQuery, triggering a query and then upon fully loading that triggering a second query. For large result sets this can stack up pretty fast, fetching 10 pages at half a second (or more) per page will result in not getting the full result set for 5 seconds (or more).

useChunkedCQLFetch work elsewhere has brought the idea of chunked and parallel fetches into view, so this work is to replace useBatchedFetch with parallelised version, useParallelBatchFetch, and deprecate the older, slower hook.

We also have a useUsers hook, which can currently only fetch ~60 users before the URL limit hits. This work will also track moving our implementations over to using useChunkedUsers, which uses that useChunkedCQLFetch under the hood.

Currently all these hooks are in stripes-erm-components, but with STCOR-730 useChunkedCQLFetch will be moved to stripes-core, and more work should be done to migrate our use cases over to that, and deprecate the stripes-erm-components version.