feat: useLocationsView hook

[pranavosu]

Description of changes

Refactor LocationsView based the WIP Hooks Api Doc.

Doesn't implement everything yet, like options for the hook but supports everything we have currently.

Issue #, if available

Description of how you validated changes

Checklist

• Have read the Pull Request Guidelines
• PR description included
• yarn test passes and tests are updated/added
• PR title and commit messages follow conventional commit syntax
• If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 726b546

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[calebpollman]

After thinking on this change a bit more think we will need to provide a single paginate action:

// where page is the target page
{ type: 'paginate'; page: number }

to allow for consuming UI components to receive a single onPaginate prop, which enables custom Paginate components to render with more than two buttons

[pranavosu]

we shouldn't have to add act here -- but we have this issue in the repo