Make db:seed command prohibitable

[spawnia]

I think it is generally undesirable and potentially unsafe to execute seeders in production databases. This change allows users fine-grained control to prohibit db:seed from running.

This is a follow-up from #55231, but only adds the Prohibitable trait without changing DB::prohibitDestructiveCommands.

Now, I have to do something like this:

// DBServiceProvider.php
DB::prohibitDestructiveCommands();
$this->app->extend(SeedCommand::class, fn (): ProhibitableSeedCommand => new ProhibitableSeedCommand($this->app->make(ConnectionResolverInterface::class)));
ProhibitableSeedCommand::prohibit();

// ProhibitableSeedCommand.php
use Illuminate\Console\Prohibitable;
use Illuminate\Database\Console\Seeds\SeedCommand;

final class ProhibitableSeedCommand extends SeedCommand
{
    use Prohibitable;

    public function handle(): int
    {
        if ($this->isProhibited()) {
            return self::FAILURE;
        }

        return parent::handle();
    }
}

With this pull request, this simply becomes this, without the need for any class overrides:

DB::prohibitDestructiveCommands();
SeedCommand::prohibit();

[andrey-helldar]

I'll just leave it here: https://deploy-operations.dragon-code.pro 🙂