When a field update fails, it should not persist anything to workspace migration table

[charlesBochet]

Bug Description

A Twenty users tried to update a SELECT enum option labels while also modifying the defaultValue. This led to a bug which is tracked elsewhere. However, this bug has put the whole workspace into a broken state instead of rolling back changes.

We have implemented transaction on the updateOneField resolver but the transaction does not take into account workspaceMigrations creation. It should, so even if we face an error, the workspace stays in a healthy state