Don't save state to localStorage on every input field change

[josephfrazier]

I suspect this may be causing latency when editing the Description
field, see https://reportedcab.slack.com/archives/C9VNM3DL4/p1672679099120099:

2 minor bugs I see on iPhone chrome browser.

1. The keyboard responds very slowly when typing in the description box.
2. when scrolling sometimes the bottom 2/3rds of the screen is white

#1 (latency) is something
@joseph Frazier
and I have talked about — when I’m typing descriptions I type them into another window (sometimes even the address bar), then copy and paste, otherwise I could die waiting

looking into the description box keyboard latency issue again, I recall
that there's some code that tries to save the state of the app to
localStorage each time the value changes. The intent of this was to make
it so that if the app is closed or crashes, then you can open it again
and pick up where you left off. However, it's possible that re-saving on
every keypress is overkill and is taxing the browser. Let me see if I
can push an update that debounces the number of saves to at most like
once/twice per second, rather than upon every key press

I do like that saved state thing, it works, but if it saved less often (or even not at all) it would be fine

I did some digging, and found that I had introduced this
save-per-keypress behavior to handle a bug where the usual saving wasn't
happening when the app was swiped away to close it:
4b22f2d

However, I'm thinking that if removing this behavior fixes the latency
issues, then it's worth putting up with edge case, assuming the edge
case even exists anymore, now that 4.5 years have passed