Get pagination params in handlers from utils

[RyanCarlisle]

Notes for Reviewers

This PR fixes #10825 : the repetitive logic for extracting page, pagesize, search, offset from API handlers and uses getPaginationParams in utils.go

Signed commits

• Yes, I signed my commits.

[welcome]

Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, you can find updates in the #github-notifications channel in the community Slack.
Be sure to double-check that you have signed your commits. Here are instructions for making signing an implicit activity while performing a commit.

[github-actions]

[864893031735973]

Ok

[vishalvivekm]

Hey @RyanCarlisle, let's discuss this on today's Meshery Dev meeting at 7:30 PM IST. I am adding this as an agenda item. Please Join https://meet.layer5.io/meshery if you are available during the meet.

[MUzairS15]

What testing have you performed @RyanCarlisle ?
Did you test the UI by building the server on this PR, did you faced any regression issues or failing APIs or incorrect results?
Did you verified if pagination and search still works fine in the UI.

[MUzairS15]

@Yashsharma1911

[RyanCarlisle]

@MUzairS15 I have tested a few APIs by building the UI and server with my code changes and the API responses were fine without any issues. However, I could not test it thoroughly as WSL/VIrtual Linux took around 5-6 GB of RAM (plus Google Chrome which took an extra 2 GB, totaling up to 8 GB) which slowed the entire system down, making it a bit difficult for me to continue testing.

[MUzairS15]

Can you list the APIs that you tested?
Are you running ui-dev-server as well?

[RyanCarlisle]

The commands that I had run were as mentioned in the guide. These were as follows:

1. make ui-build
2. make ui-setup
3. make server
4. make ui

I have not made a list but I shall try to make a list of the APIs after testing them out again.