I am not sure if there is a rationale behind ignoring extra keys like
this. I was under the impression that something might copy options to
platform specific options, thus leaving options in the original array,
knowing they would be ignored anyway. If it is the case, it would be
best to just move them, otherwise, this commit might help troubleshoot
some mapping issues.
I had to fix some tests that wrongly used that options array (maybe
these options were valid at some point?).

it is best practice to implement retry logic for transactions that are aborted because of deadlocks or timeouts. this makes such method available inside the DBAL and also add detection for errors where retrying makes sense in the different database drivers

[DBAL-722] Introduce subclasses for runtime relevant exceptions (NotNull, DuplicateKey, ForeignKey Constraint Violation).