(#3502) Return the PageSize if specified

[corbob]

Description Of Changes

If a page size has been specified, use it. Also emit a warning if it's something other than 30 as there are known issues with some feeds.

Motivation and Context

Make a few things clearer and easier when working with Sleet and other feeds.

Testing

1. Setup Sleet as per Use the user-provided page size when querying repositories #3502 (comment)
2. Run choco search -s http://localhost/index.json.
3. Ensure that the page size is being used in queries to Sleet.
4. Run choco search -s http://localhost/index.json --page-size 5.
5. Ensure only 5 results returned along with a warning about the page size differing from 30.
6. Run choco search -s http://localhost/index.json --page-size 50.
7. Ensure that 50 results are returned along with a warning about the page size differing from 30.
8. Run choco search -s http://localhost/index.json --page-size 500.
9. Ensure that an error is displayed indicating that the page size cannot exceed 100 (this did not change in this PR, is just a soundness check)
10. Run choco search -s http://localhost/index.json --page-size 100.
11. Ensure that 100 results are returned along with a warning about the page size differing from 30.

Operating Systems Testing

• Windows 10 22H2

Change Types Made

• Bug fix (non-breaking change).
• Feature / Enhancement (non-breaking change).
• Breaking change (fix or feature that could cause existing functionality to change).
• Documentation changes.
• PowerShell code changes.

Change Checklist

• Requires a change to the documentation.
• Documentation has been updated.
• Tests to cover my changes, have been added.
• All new and existing tests passed?
• PowerShell code changes: PowerShell v3 compatibility checked?

Related Issue

• Fixes Use the user-provided page size when querying repositories #3502
• ENGTASKS-4086

[corbob]

This PR is in draft while I formalize the testing and other aspects of it.

[vexx32]

This looks like it works correctly in testing, and the code looks pretty code so far. Nice work!

[vexx32]

Code looks good, but am realising we should definitely add a regression test for this in terms of functionality.

[vexx32]

That looks good, thanks for sorting this out! 💜