Detect empty V2 server responses at ServerApiCall level instead of ResponseUtil level

[anamnavi]

Previously for scenarios where a package could not be found on the server, V2ServerApiCall responses returned were non-empty XML responses, so an error indicating package not found was not detected and errRecord was not populated. This meant that at the ResponseUtil level the response would try to be converted to a PSResourceInfo and throw an error and we would catch and error handle in FindHelper for the "Package not found" scenario.

This PR changes that. The parameter $inlinecount=allpages is added to the V2 request so that count is always returned in the response. This is used to detect a "Package not found" scenario and then an errRecord with FullyQualifiedErrorId "PackageNotFound" is returned and detected in FindHelper to properly error write or write verbose.

Changes were also made to the other ServerApiCalls classes to consistently return errRecords with FullyQualifiedErrorId "PackageNotFound" when a package isn't found.

PR Summary

PR Context

Resolves #1349

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.