Fix --no-interaction SQLite file prompt

[jacksleight]

Fixes #352

This prompt comes from the migrate command, and by the looks of that the only way to ensure the SQLite file is created without a prompt is to add --force. Adding --no-interaction to migrate results in no file being created, which then errors when the migrations run.

Hopefully this is OK but let me know if you'd like any changes.

[stancl]

(Disregard, issue was somewhere else, see linked issue below)

Not sure if I'm doing something wrong, but even on laravel/installer:dev-master I'm getting

The SQLite database configured for this application does not exist: database/database.sqlite.

with:

laravel new --no-interaction --git --jet --stack=livewire --api --verification --pest --database=sqlite test

Also, --force having an effect here seems wrong since the --help comment for --force is:

Forces install even if the directory already exists

So that behavior should all be under --no-interaction.

Either way, on the latest dev-master, the command above prompts me for both creating the DB and re-running migrations, and --force doesn't change anything 🤷🏻‍♂️

Confirmed with composer global show laravel/installer that I'm using the right commit:

source   : [git] https://github.com/laravel/installer.git db5f79dda5bd9b84c0777da435d2147c5caa4068