[Bug]: Fix affected components

[Ivan-Shaml]

Describe the Bug

Because of fix for FAForever/faf-java-api#1004 now some components don't show the data properly. Pagination needs to be introduced for:

1. PlayerInfoWindowController (all tabs are affected)
2. CoopController
3. LeaderboardDistributionController
4. SimpleHttpFeaturedModUpdaterTask
5. TutorialController (not enabled)

Log file or Error Message

None

Reproduce the bug

Open info for some player, or any affected view.

Expected Behavior

The data is loaded correctly, using pagination.

Screenshots

For example:

Additional context

No response

Which Operating System are you using?

Windows

[Brutus5000]

If we find endpoints that require much more data, we should add dedicated API endpoints and no scrape 100 pages instead. That would kind of defeat the purpose and make the client hit the rate limit thresholds.

[Brutus5000]

Also affected: mod/map/replay reviews

[sulikdan]

Hmmm, have a few question here:

• I assume this is master ticket and we will slowly hammer it - one by one right?
• Do we have some sort of pagination template?(So I can inspire, if I start to work on it.) Or are we reinventing wheel altogether?
• Wouldn't it be reasonable to cache/persist some of these data at the user side (if they are not already saved)?

P.S.: Sorry for dumb question that I could read from code, but I don't have time for that lately as I've changed to a new job and its partially legacy code nightmare ...

P.S.2: Maybe I will need someones help to get API/BE running locally.

[Sheikah45]

We do use pagination in other places the old max was just used for things where we wanted to one shot load easily because the screen doesnt exactly work with pagination like the graphs