Support read after write logic

[schauder]

In order to utilise triggers and default values a read-after-write logic should be supported.

see also spring-projects/spring-data-commons#2158

[schauder]

For some database a returning clause could be used. For others we would need to actively select the data.

I'm not sure how we should choose if we do apply any read after write logic.

Maybe returning the entity from the method?
After all we would need a return value for the cases where the changed properties aren't writable.

[b-dkordonski]

Can't you just support returning on database engines that provide it? In jooq with R2DBC this works OOTB, I'm surprised that such basic functionality is missing here.