Add options config for backup/restore commands

[timkelty]

Description

The PR allows \craft\config\GeneralConfig::backupCommand and \craft\config\GeneralConfig::restoreCommand to be an options array to configure how the commands are generated.

Goals

• make small tweaks easy (eg ignore a single table). Currently this can only be done via event.
• make it easy to opt-in to postgres's archive format (possibly make this the default for v5?)
• make it clear when things are going to be replaced or merged (eg ignore-tables)
• provide a way to tap into command for modification
• be non-breaking

Valid values include:

<?php
use craft\config\GeneralConfig;
use mikehaertl\shellcommand\Command as ShellCommand;

return GeneralConfig::create()
    ->restoreCommand([
        'archiveFormat' => true, // pgsql-only

        // example: add an arg
        'callback' => fn(ShellCommand $command) => $command->addArg('--verbose'),
    ])
    ->backupCommand([
        'ignoreTables' => ['foo', 'bar'],
        'archiveFormat' => true, // pgsql-only

        // example: remove an arg
        'callback' => function (ShellCommand $command) {
            $command->setArgs(str_replace('--dump-date', '', $command->getArgs()));

            return $command;
        },
    ]);

etc…

• I ended up leveraging mikehaertl\shellcommand\Command because it was there and were already using it. Easier than stitching strings together.
• To keep backward compat, ignoreTables can either come from the EVENT_BEFORE_CREATE_BACKUP or from the new ignoreTables option. If both are present, the event will take precedence.
• The callback could easily be an event instead, but it seemed like it might be a pain to add an event listener just to add an additional arg.

[brandonkelly]

The options array is keyed by the db driver name

This feels like unnecessary complexity to me. No project uses both.

[timkelty]

@brandonkelly yep, already nixed it. Flipping to draft while I tweak some things.

[timkelty]

Moved to \craft\db\DbShellCommand

[timkelty]

Moved to \craft\db\DbShellCommand

[timkelty]

Moved to \craft\db\mysql\BackupCommand

[timkelty]

Moved to \craft\db\mysql\RestoreCommand

[timkelty]

Moved to \craft\db\pgsql\BackupCommand

[timkelty]

Moved to \craft\db\pgsql\RestoreCommand

[brandonkelly]

@timkelty After reading #14648 (comment) I’m wondering if it would make more sense to just add a bunch of new top-level config settings for this. Brad is suggesting using a multi-env config in response, which we are sortof moving away from in favor of environment variables, but it doesn’t seem like it will be possible to use environment variables here as currently implemented. (Besides pulling them in manually from config/general.php via App::env().)

[timkelty]

Closed in favor of #14897