Restore the pruned database migration files

[outdooracorn]

Restore the pruned database migration files to make discovery of past migrations easier. The generated schema file will still be used on installs where no migrations have been executed.

In 1cd71f4, the php artisan schema:dump --prune command was run, to squash database migrations into a schema file1. This was done as part of the Laravel 10.x -> 11.x migration, in order to avoid having to update any existing migrations that use the ->change() method2.

The --prune option removes all existing migrations that are squashed into the schema file. This option is not required by the 11.x migration docs2, and makes it harder to view historical migrations.

From the Laravel 11.x docs on Squashing Migrations1:

Now, when you attempt to migrate your database and no other migrations have been executed, Laravel will first execute the SQL statements in the schema file of the database connection you are using. After executing the schema file's SQL statements, Laravel will execute any remaining migrations that were not part of the schema dump.

Therefore, this only has an impact on local development/CI, and there is no issue with having both the migration and schema files present in the repo.

Bug: T440599

[deer-wmde]

I tested it with minikube and skaffold and did spot a INFO Nothing to migrate. in the logs ✔️