Fix false positive changes for generated columns by updating snapshop

[podoko]

After persisting or updating an entity having columns with the configuration generate: 'ALWAYS', the persister was updating the data on the entity but not notifying the UnitOfWork. This led the entity to be considered dirty in subsequent flushes, triggering lifecycle events. This was especially noticeable when the database field was mapped to a DateTime

This PR makes the persister update the UnitOfWork with the new values from the database. By doing this, UnitOfWork::computeChangeSet does not consider these fields as different from the ones in the database.

Note that if the user does something like $entity->nonUpdatableField = 'new value', the unit of work will again consider the entity as dirty and the field appear in the changeSet. This problem is addressed in #12385

Fixes #12017

[podoko]

I upgraded the tests in order for them to run with dbal 3.7

[github-actions]

There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.
If you want to continue working on it, please leave a comment.

[podoko]

I am still working on it