Avoid aggregating the total items associated with a rollup when fetching elements filtered by that rollup

[PJColombo]

When fetching multiple blobs or transactions filtered by a rollup, an additional Prisma call is made to count all rows associated with that rollup. This approach is highly inefficient, as it occurs with every request, significantly impacting performance.

We should consider updating this logic to retrieve the total number of elements associated with the rollup from the stats table, once rollup stats support is implemented.

blobscan/packages/api/src/routers/blob/getAll.ts

Line 80 in a8b94e2

// TODO: this is a workaround while we don't have proper rollup counts on the overall stats