Performing Permalink/blocks search might require loading extra data

In the current API implementation of both permalink and block search pages, there is room for more data to be loaded, particularly when the user has filtered data. So we need to take this into consideration when the API call returns a block range that does not start with block 1.

Below screenshot of complete data set result (no more page ranges can be loaded)

Below is an API call result that can still return additional page ranges

So on the front end, next to the pagination, if there are potentially more page ranges that can be loaded, we need to add a button "Load More", which when clicked will be able to fetched additional pages/data sets instead of being limited to only the first set of results being returned. Otherwise we will only be able to go through results up to 10 pages, which is a limiting experience.

per below, currently we only show up to 10 pages, the new button will sit next to the page "10" and will allow loading more data.

In such cases where not all pages were returned on the first query, we will also need to adjust the number of results so that, instead of saying "A total of 1000 permlinks found", we get "1000+ permalinks found" as there is room to fetch more data

@mzander can share more details if needed for whoever is gonna be working on this.