handle record updates and account deletes
- bug from jetstream oxide: https://github.com/videah/jetstream-oxide/pull/9
- locally just merging create and update into a single variant, switching on `operation` in client
- mod cursor seeks with bounds instead of prefix.next, since post prefixes will be delete tombstones
- the exclusive bound is *super* annoying. this pulls lsm-tree in but that was not even nice. should ask fjall to expose the upper bound calculation as a distinct function?