Spurred by #10452 and #10549
Partially addressed already with #10567 and #10561
Overlaps somewhat with #10587

Basically, I think the pagination logic could have some extra "safety nets" and some other UI niceties to help avoid user confusion and keep the UI feeling responsive. This would affect the following tables:

• Users table
• Audits table
• Workspaces table

Safety nets and bug fixes

1. Make sure that if the user accidentally navigates to an "invalid" table page, there's something (automatic or manual) that makes it easy for them to get back to a valid page (right now, the page navigation UI disappears entirely)
2. Make sure that when the user changes pages, the browser will always bring them back to the top of the table (but maybe make it so that this doesn't happen if they start scrolling or doing anything while waiting for the new data to load in? Don't want to hijack their controls if they're in the middle of something)
3. Make sure data for each page is cached properly, so that if you go to a page you've already visited, you see the data immediately

Niceties

1. After a new page loads in, prefetch the next and previous pages (when it makes sense)