stage.corkboards.me update

Changes deployed to stage.corkboards.me for testing:
- Dismissed notes now have an 'undo' option that lasts 20 seconds
- Nested nevents should render more consistently
- Video filter includes: a) video note kinds b) links to video on platforms c) direct video file links
- Video player shows loading progress and 'open in new tab' fallback
- Columns save on a per-corkboard, per-device basis, and columns can now be changed on mobile (default 1)
- Threads should load with relevant context / entire thread more consistently
- 'Referenced Note Not Found' should appear less frequently
- Reacted-to content should render in threads more consistently
- If 'Load Newer' finds no notes, it still resets the 'time-since' indicator
- Saved for Later tab changes: Green/Red triangles appear without hovering; clicking the text area of a minimized 'Saved for Later' note opens it instead of opening the thread modal; removed superfluous chevron and 'no notes found' message; setting of which notes are minimized and which are open is saved to backup

### Corkboards.me 1.92 Alpha

Staging changes tested, deployed to corkboards.me with bugfixes:
- Newly posted notes appear in UI immediately
- Me tab relevant loading text wasn't appearing
- Stats no longer ellipsed in phone mode, not overlapped on large screens
- Load Newer button shows how much time of notes haven't been fetched yet on this corkboard

Test

### stage.corkboards.me update

Changes deployed to stage.corkboards.me for testing:
- Logout shows as option in phone mode
- 'Load all newer notes' fixed on 'me' tab
- **Footer tray redesign**
- Added toggle for 'Show Unpinned Notes' on Me tab
- 'Select from your follows' field in 'New corkboard' modal shows 500 npubs at a time instead of 100
- Initial load includes caching profile information
- Outbox model on all fetches so that all notes and profile information is found, and so that user sovereignty is respected (we look where writer has written rather than seeing whether some global relay set has decided to archive him)
- Separate caches per tab, so that loading more notes on a custom corkboard doesn't cause issues with loading more on other corkboards

### Corkboards.me 1.91 Alpha

Staging changes tested, deployed to corkboards.me with bugfixes:
- Kind 10001 used for pinned notes (consensus standard) so they can appear in other clients that support that kind
- Pinned notes fetched first from npub's write relays
- More relevant waiting text and 'no notes found' text

### stage.corkboards.me update

Changes deployed to stage.corkboards.me for testing:
- Rerties fail gracefully so there aren't infinite websocket attempts if connection is lost
- Switching to a corkboard shows cached notes immediately, then fetches newer notes in background, rather than the other way around
- Can repost a note from the corkboard, not just inside the thread modal
- Minor UI improvements

### Corkboards.me 1.9 Alpha

- Turns out without stage at an isolated subdomain, caching can get mixed. stage.corkboards.me is still propagating, so corkboards.me top level domain has newest.
- Fixing above resolved the unsolved mysteries, so fixing note fetching was easy. Load 25 or 100 notes at a time, and optionally set a 1x2x3x multiplier
- May have made the fetching a bit more reliable and faster by including fallback relays with the logged in npub's outbox relays for the 'more notes' fetches, with a lower timeout
- Minor UI edits
- Corkboards with only one npub show profile information

Changes deployed to corkboards.me/stage for testing:
- Visible / Dismissed / Filtered / Total counts
- Custom corkboards just load right from cached prefetch of all follows recent notes, and only look to relays for any npubs outside of follows, or to internet for rss feed info.
- Fetch 100 notes button was not working even though 10 button was. The 2nd and 3rd buttons and the combination of 'add # notes' and 'add # of hours' was causing clod ridiculous problems. I don't like removing choice, but here I removed and changed a lot to result in what works, and to rid unecessary complexity. I'm dum on storage (and most things, really) so not sure if the architecture is ideal. The rest is up to experts in the next phase.
- What I ended up with this iteration is to estimate a time window that will fetch the requested amount of notes based on what notes are already there. i.e. if the last 25 notes were posted in an hour, fetch another hour. If that's not enough, fetch again. As a result, if you click for 25 more, you get 25ish more.
- Because above is so much more than a bugfix, I ran a tech debt audit and asked for / implemented suggestions.