Fix top value when top is not provided

[najagasi]

Description

This PR is to revert the changes that are made in this PR dafc0d9#diff-5fcd32ad9abc940415b096a7b99c3f3882e4c27dd7806430212796a347c94952
its causing requests made to the RP with top=2147483647 when no $top is requested.

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here

[pilor]

This isn't descriptive enough. Say something about reverting a change in 1.4.0 to pull in all pages by default. Default page size is now 'X' for Get-AzPolicyState

[najagasi]

pagination is not yet supported in powershell it is to be implemented, not sure how to word this without using word page.
when a user does not provide top we return 1000 rows, once paging is supported here we will send in 1000 rows plus a nextLink.
the description for this release was support pagination, do i need to instead say "unsupport pagination"

[pilor]

Let Liz/Kemley word it :-) However, you definitely need to mention which cmdlet this affects

[najagasi]

Will add "Retracting changes made in powershell that increased request row limit. Removed incorrect statement of supporting paging" as suggested by Kemley

[msJinLei]

@najagasi Please do not add new version to changelog and just put new items under upcoming release