Remove forListVersion from item updates?

[greenlucid]

With account abstraction, you could batch transactions and revert if listVersion has changed.

Without account abstraction, removing this would be a security hazard, since list owners could frontrun an update to the list and change the policy in a way that's destructive to the submitter. So, that's the rationale. Just putting it as an issue to let it be documented.