Take aggregate locks before existence checks in create-vs-delete flows
When create-new-version and delete-final-draft share a PostgreSQL advisory lock, acquire that lock before checking the aggregate parent exists. Checking first allows creation to observe a parent that a concurrent delete later removes, then resume after the lock and fail with an u…