fix: limit items on response from ERS

[PashaFG]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• The changes are appropriately documented (if applicable).
• The changes have sufficient test coverage (if applicable).
• The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:

Issue: #3698

But to the number of elements available for return in the authFetch('versions/sorted') endpoint, if we add an update to an older version. Since in the first N (default: 50), sorted by version name, we do not get the newly created one.

This number is regulated on the electron-release-server side. https://github.com/ArekSredzki/electron-release-server/blob/master/config/views.js#L46

To solve the problem I added a loop refetch versions list, if in response we receive a number of elements less than indicated in request.key total.

I also update interface ERSVersionSorted, because page in response has type string | number, page in ERS takes from query params, but default value is number "0"

[PashaFG]

Good day.

Within the framework of this PR, a more optimal solution to the problem of searching for the required version was found.
This change allows us to reduce the publisher's logic and transfer the logic of searching for the version we need to the ERS.

In the current solution, we no longer need to use a hack with the API intended for the UI part of the application and can return to a method specifically designed for this

I will be glad to receive your review of this solution!