Added correct counting of licenses seats through pagination

[Godmartinz]

Description

The lIcenses seat number would restart if the page was changed. Now licenses seats count continues through pagination

Fixes #14067

Type of change

Please delete options that are not relevant.

• [ x] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• PHP version:
• MySQL version
• Webserver version
• OS version

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[what-the-diff]

PR Summary

• Introduction of page-based navigation in License Seats Controller
  The License Seats Controller, which oversees the management of license seats in the application, now can understand 'pages'. It basically means faster and more efficient browsing for users when going through their license seats data.

• Changes in the logic for counting license seats
  A renewal of the method which counts the license seats was made in the related file. This change accommodates the addition of 'pages' and improves the accuracy of the count, especially when browsing through different pages of data. This ensures users always see correct numbers in their interface.

[marcusmoore]

Edit: See comment below

---

Previous comment:

I like this but it would be good to handle API requests from outside of our application as well.

For example, the requests that the table on the license show page fires has sort and order in it:

https://snipe-it.test/api/v1/licenses/1/seats?sort=name&order=asc&offset=10&limit=10

The sort=name doesn't really matter but order=asc does...if I fire a manual request using the example in the API docs, which does not include order=asc, the results don't match up:

But if I add order=asc then the results line up:

Should we always add order=asc to the query so the results are the same no matter the context?

[Godmartinz]

@snipe if we want to only sort by ascending let me know, I'll edit this PR. But the seat number doesn't really matter for licenses right?

[marcusmoore]

@Godmartinz asked for clarification about this and I think my overall request makes sense but the implementation would be outside of the scope of this PR.

[snipe]

Gentle ping, @Godmartinz

[snipe]

Gentle ping again, @Godmartinz

[Godmartinz]

whoops missed this, fixing...

[Godmartinz]

@snipe a check on offset is performed prior to setting the $seat_count