Persist pagination state in url

[emma-sg]

Closes #1944

Changes

• Pagination stores page number in url search params, rather than internal state, allowing going back to a specific page in a list
• Pagination navigation pushes to history stack, and listens to history changes to be able to respond to browser history navigation (back/forward)
• Search parameter reactive controller powers pagination component
• Pagination component allows for multiple simultaneous paginations via custom name property

Manual testing

1. Log in as any role
2. Go to one of the list views on an org with enough items in the list to span more than one page
3. Click on one of the pages, and navigate back in your browser. The selected page should respect this navigation and return to the initial numbered page.
4. Navigate forward in your browser. The selected page should respect this navigation and switch to the numbered page from the previous step.
5. Click on a non-default page, and then click on one of the items in the list to go to its detail page. Then, using your browser's back button, return to the list page. You should be on the same numbered page as before.

[SuaYoo]

Pagination looks great. I tested with workflows, archived items, collections, collection items, and browser profiles, going backwards and forwards in browser history.

Let's cherry pick eb0472e into a separate branch though, to keep the scope of this PR (and squashed commit) to pagination?

[emma-sg]

Yep, makes sense. Moved it to #2538, and removed from this PR.