UX wishlist for "refresh"

There are various cosmetic things I would hope to have on this page:

- [ ] Refresh
- Higher order feedback: why are we even offering a first class refresh button or doing automatic refresh? This is a slow changing table (i.e., we aren’t going to get dozens of SP’s per day). Let just lets someone refresh the page if they want to see the latest (but make sure the URL is bookmarkable so a refresh gives the updated view.)
- If we are doing auto refresh…
- Can we refresh in the background without covering up the content of the table with a “refresh” mask?
- Lets auto refresh much less frequently

---
Previously completed items or items backlogged elsewhere
- [x] Have bookmarkable URLs like https://github.com/FilOzone/filecoin-cloud/issues/64
- [ ] #68
- [x] Table improvements like https://github.com/FilOzone/filecoin-cloud/issues/139
- [x] #69

----
This has a lot of similarities to https://github.com/FilOzone/filecoin-cloud/issues/140

No files, tests, or entry points are named. Compare the requested refresh behavior with issue #140 and the completed URL and table work referenced in issues #64 and #139. Done means the refresh approach is defined, bookmarkable URLs remain usable, and the table is not obscured during any background refresh.

Written by the indexing model from the issue text.