fix(ui): ListWatch should not _both_ set and depend on nextOffset

[agilgur5]

Fixes #12663, fixes #12626 (as well as #12025 (comment) 2.i, the one with the browser network tab screenshot)
Follow-up to #11891

Motivation

The ListWatch previously both depended on and set nextOffset, which was recursive

• note that it technically does depend on it since the list uses the whole pagination object, but nextOffset only changes within the effect or at the same time as another pagination
  • so it is safe to remove as a dep
• when pagination was enabled, this recursive dep/set would cause a duplicate request
  • in my repro, I only had one duplicate request, as after that nextOffset stayed consistent. would have two for each page move
    • for other folks in UI: Workflow list blocked when limit applied #12663 and UI infinite SSE creation + timeout on Chrome #12626, this seemed to have caused an infinite loop, but I was not able to repro that specifically as nextOffset is constant after the duplicate
  • the quick succession of these duplicates also somehow made some of the SSEs impossible(???) to stop; even calling listWatch.stop() would not stop them
    • this would result in SSEs continuously growing until the browser connection limit was hit and then no new connections being allowed, halting all network activity
    • notably, I confirmed that the effect clean up and listWatch.stop() was occurring (through logs and other debugging), it just seemed to not close the SSE for some reason (???)
      • I have not been able to root cause that, but this fix makes that problem disappear for now at least
        • it might be an RxJS issue (notably there is some usage of deprecated functions) or a Server issue, or an SSE issue, not sure

Modifications

• remove nextOffset from the ListWatch's useEffect's deps array

• also fix a typo I had in the query param retrieval of offset

  • I had accidentally written the literal name instead of putting the actual name of the param, offset, woops 😕

• plus consistently ensure that the pagination defaults are undefined everywhere, so that the useEffect deps do not change

  • removes more unnecessary network requests / compute / memory / etc
    • esp. with the quick succession of SSEs problem above, definitely want to limit this to only as much as is needed

Verification

In my partial repro, the network waterfall looked like the below, with duplicate SSEs that were not always cancelled:

After this fix, it now looked as intended, only one SSE at a time: