Optimise REST calls for fetching resource

[almightyrush]

Describe your enhancement idea

Currently for fetching CICS resources, it does 3 REST calls.

1. Generating a cache token and fetching record count
2. Getting the first page based on the count
3. Invalidate the cache as its the last page (also the first page).

This also happens if the data is less even to paginate. This adds some latency for performing actions on resources or fetching small set of records where pagination is not required.

A suggestion to optimise it is:

1. Generating a cache token and fetching record count.
2. Check if the record count is less than the paginate limit and fetch the records without NODISCARD.

That will prevent the unwanted additional call.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.