Add --force option to MigrateFresh

[justasbrandlions]

Bug description

No way to override in configs --force flag when running migrate-fresh. This might cause huge problems by accidentally running this command on production with hundreds of tenants.

Steps to reproduce

set .env to production and run php artisan tenants:migrate-fresh

Expected behavior

I'd expect tenants:migrate-fresh would ask me for confirmation on production env, but it's not. It sets the --force to true and removed all tenant DBs on production without any confirmation.

Laravel version

10

stancl/tenancy version

3.7

[stancl]

Not much point in this since if you're running migrate-fresh you're already explicitly asking for your data to be deleted, but I can add an argument for this.