Postgres has a `SERIAL` data type to allow shorthand for
`nextval('sequence_name')`, but DDL like this:

    CREATE TABLE example (id SERIAL)

Cannot be generated in the DBAL schema APIs.

And then we don't need to wait till v3 to not require comments on the
JsonType.

On 31d01283 we made JsonType the default
one, which caused some unexpected results with the comparator.

This tests validates that if users have a JSON column but are using the
JsonArrayType we'll just add a comment to the column.

Reference: https://github.com/doctrine/dbal/pull/2782

statements in a rewindable iterator. Skipped the test for iterating
multiple times with a message regarding that iterators are non
rewindable.

Only added to mysqli for now, can add to other drivers (assuming they
support reseting the pointer in some way) after feedback.

Test fails because it's not possible to reuse a generator in this way.

It is a somewhat fragile thing to do.

It was not covered, probably because it was hard to do something
generic. I choose to duplicate some tests instead, so that things stay
relatively simple.

#2821 replacing `@group` annotations with proper references, since DBAL-* issues are from JIRA, not Github

Added upgrade notice about BC break.
Cleanups

Changed DBALException::invalidPlatformSpecified() exception to be more detailed about what was given.

Fixed cs issues

Fix PSR2 rules : "As per PSR2, the static declaration should come after the visibility declaration."

#2794 adding tests verifying the regression, `DateTimeImmutable` should STILL work, even if unintentionally

Since it was deprecated.

If you pass a null to the where array of update or delete it's
pretty obvious what you want.

Most (all?) databases won't match anything if you actually try
to compare with NULL making this a silent failure without it.