Also onChangeUseResult > onSubmitUseResult
and onChangeStatus > submitStatus

The reason is because the action is being referred to as submit
everywhere else. Even the function that triggers the submit is
called "submit". This was called onChange, because according to
the internal useParcelState hook it is just a change, but the
name should really reflect how its used

frameMetas job is to hold data that should only exist
until the next change occurs (the current parcel frame)

lastOriginId requires that same data lifespan

lastOriginId was a concept that only react-dataparcels
was interested in, and probably shouldnt have been put
in plain dataparcels

Feature/on submit

replacing the inner parcel from props is intended to be a complete reset,
so the buffer should also be emptied

when no rebasing and new data is received from props, buffer is wiped and buffers state is replaced with data from props
when rebasing and new data is received from props, buffers state is replaced with data from props with buffer applied to it
also fixed a wrong test that was relying on incorrect cachebehaviour in a change request

Refactor lastOriginId and add mergeMode