Enforce collation/charset more heavily

[g105b]

Every so often, a project of mine struggles to apply a migration because there's a charset mismatch between tables, which shouldn't be possible really.

I will add the following to WebEngine's defaults, and track here accordingly:

charset=utf8mb4
collation=utf8mb4_general_ci

[g105b]

I didn't understand the problem I was having, so I asked an LLM:

Migrator Fix

The current gt migrate path should enforce schema defaults every time. In Gt\Database\Migration\Migrator::selectSchema(), don’t only create the schema if missing. Also alter the existing schema default:

$this->dbClient->executeSql(
	"create schema if not exists `$schema` default character set {$this->charset} default collate {$this->collate}"
);

$this->dbClient->executeSql(
	"alter schema `$schema` default character set {$this->charset} default collate {$this->collate}"
);

$this->dbClient->executeSql("use `$schema`");

That makes later create table migrations inherit the configured/default collation.

Also patch Gt\Database\Cli\ExecuteCommand::buildSettingsFromConfig() to pass config collation/charset into Settings. Right now it builds Settings without those config values. It should pass:

$config->get("database.connection_name") ?: DefaultSettings::DEFAULT_NAME,
$config->get("database.collation") ?: DefaultSettings::DEFAULT_COLLATION,
$config->get("database.charset") ?: DefaultSettings::DEFAULT_CHARSET,

Finally, I’d still keep explicit table-level charset/collation on migrations that create FK tables, because it makes the migration self-contained:

)
character set utf8mb4
collate utf8mb4_general_ci;