For testing purposes and not only, it may be needed to evaluate an arbitrary SQL expression (see https://github.com/doctrine/dbal/pull/3013, https://github.com/doctrine/dbal/pull/3108). Instead of doing `str_replace()` on an expected string, one could specify the expression explicitly.

A string is made of characters, an array might contain anything.

array_merge will not work with any iterable

This reverts commit e3ab1276, reversing
changes made to f988b0a6.

It is now possible to use `\` in non-escaped default values for a column,
and it will be automatically escaped for platforms that need it.

Previously this lead to a confusion when diffing actual and expected
schema leading to perpetual out of sync schema.

Before:

```php
/**
 * @ORM\Column(options={"default" = "Foo\\Bar"}))
 */
private $name;

```

After:

```php
/**
 * @ORM\Column(options={"default" = "Foo\Bar"}))
 */
private $name;

```

And the result in database will be a default value exactly as written in
the annotation, that is `Foo\Bar`.

It is a somewhat fragile thing to do.

It groups things naturally.

cover in test suite that platform throws exception on generating inline column comment SQL if unsupported

fixes #2270

Fixed inconsistent use of getSqlDeclaration method name

each $part does not contain ".", so quoteSingleIdentifier may be called directly thus avoiding recursive strpos checks.