The CHARACTER SET keyword is split with a new line

[Menelion]

Bug Report

Q	A
Version	1.5.1
Previous Version if the bug is a regression	N/A

Summary

Whenever a Doctrine migration is created with --formatted option, i.e., SQLFormatter is used under the hood, the DEFAULT CHARACTER SET statement is formatted in quite a bizarre way, see steps to reproduce.
I'm using MariaDB 11.2.2 on this machine.

Current behavior

Now it's like this for some reason:

          [...]
          PRIMARY KEY(id)
        ) DEFAULT CHARACTER
        SET
          utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB'

Expected behavior

I would expect rather:

          [...]
          PRIMARY KEY(id)
        )
        DEFAULT CHARACTER SET utf8mb4
        COLLATE `utf8mb4_unicode_ci`
        ENGINE = InnoDB'

How to reproduce

Basically, make a migration with doctrine:migrations:diff --formatted or, if you are like me into Symfony, with make:migration --formatted. Here's one full migration for reference:

<?php

declare(strict_types=1);

namespace DoctrineMigrations;

use Doctrine\DBAL\Schema\Schema;
use Doctrine\Migrations\AbstractMigration;

final class Version20250109223941 extends AbstractMigration
{
    public function getDescription(): string
    {
        return 'Created languages table';
    }

    public function up(Schema $schema): void
    {
        $this->addSql('CREATE TABLE languages (
          id INT AUTO_INCREMENT NOT NULL,
          position SMALLINT UNSIGNED NOT NULL,
          code VARCHAR(20) NOT NULL,
          english_name VARCHAR(100) NOT NULL,
          native_name VARCHAR(100) NOT NULL,
          PRIMARY KEY(id)
        ) DEFAULT CHARACTER
        SET
          utf8mb4 COLLATE `utf8mb4_unicode_ci` ENGINE = InnoDB');
    }

    public function down(Schema $schema): void
    {
        $this->addSql('DROP TABLE languages');
    }
}

I tried to dig in deeper to understand how to fix that, but so far I probably spent too little time on it, have no idea how it can be fixed appropriately.

[mvorisek]

This library does not intend to parse full SQL grammar.

Both CHARACTER, SET are reserved keywords and per MySQL https://dev.mysql.com/doc/refman/8.4/en/create-table.html grammar there cannot be anything in between, the SET can be "weakened", ie. not assumed to be an isolated SET keyword used frequently in UPDATE ... SET ..., when CHARACTER is before the SET keyword.