feat(database)!: allow setting char size

[regnerisch]

Until now it was not possible to set a specific CHAR size inside the migration:

->char('uuid')

With this PR, users are now forced to set a CHAR size:

->char('uuid', 36)

As Postgres and MySQL consider the previous foo CHAR as foo CHAR(1), this seems to be a breaking change. So maybe changing private int $size = 1 would be better?

Postgres:

If character (or char) lacks a specifier, it is equivalent to character(1)
(https://www.postgresql.org/docs/current/datatype-character.html)

MySQL:

If M is omitted, the length is 1
(https://dev.mysql.com/doc/refman/8.0/en/string-type-syntax.html)

[innocenzi]

While this is definitely a breaking change, I think that's something we want here, be more explicit 👍

If you use CHAR, it's generally because you expect a specific length, so it doesn't make sense to have an implicit 1 as a default

[github-actions]

Benchmark Results

Comparison of 3.x against 3.x (f1162475c1a432bec8d9c8442f46f7c895db7765).

Open to see the benchmark results

No benchmark changes above ±5%.

_{Generated by phpbench against commit 03ae720}

[brendt]

Let's set the default to 1, that way it's not a breaking change and I think it makes sense for 1 to be default.