Use new validated commit

[neekolas]

tl;dr

• Uses validated_commit_v2 everywhere
• Renames validated_commit_v2 to validated_commit

More info

• The new validated_commit struct includes a diff of all metadata changes. This requires a change to how we evaluate permissions, which previously had to figure out the diff as part of evaluation. This should be easier to test and work with.
• Using the new validated commit requires a bunch of functions that were previously synchronous to be async. We are using the await_helper to wrap these synchronous functions in async functions. We are going to have to watch this carefully for deadlocks. Alternatively, maybe we want to create an async_transaction function on our DbConnection that works similarly to the existing transaction function but allows for an async callback.

[neekolas]

• #741
• #740 👈
• #739
• #718
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @neekolas and the rest of your teammates on Graphite

[neekolas]

I'm going to merge this now so that @cameronvoell can keep working on permissions on top of identity-release. But feel free to keep commenting or adding notes and I can fix in a subsequent PR