Migrations - re-initialize ahead of v1.0 release

[geoff-maddock]

Re-initialize migrations for the 1.0 release and create a process to re-sync them until that release happens.

• Clean up the database and confirm the schema is correct
• Delete old migrations
• Re-create migrations from the state of the schema and seed the database with initial data
• Create "bare", "basic", "pittsburgh" and "arcane" initial data sets as sql and as seed-like commands
• Add "bare" data to the migrations
• Run through a test deployment with each set?

If I need to change something before 1.0, re-run the above.

There is a "squash migrations" feature in laravel 8. https://laravel.com/docs/8.x/migrations

Relates tp #377

[geoff-maddock]

https://laravel.com/docs/8.x/migrations#generating-migrations

php artisan schema:dump

// Dump the current database schema and prune all existing migrations...
php artisan schema:dump --prune