Make migrations robust

[grantfitzsimmons]

Migrations are failing quite regularly, and the user is often not notified of the failure until the app tries to access a particular field/table that is not available to it.

This manifests in errors such as the common
Unknown column 'spmerging.status' in 'field list

This issue is due to the the original migration using the field name mergingstatus:

specify7/specifyweb/notifications/migrations/0003_spmerging.py

Line 21 in 1419cd7

('mergingstatus', models.CharField(max_length=256)),

Later, we changed the name of this field (among others) to status:

specify7/specifyweb/notifications/migrations/0005_auto_20240530_1512.py

Lines 15 to 19 in 1419cd7

	migrations.RenameField(
	model_name='spmerging',
	old_name='mergingstatus',
	new_name='status',
	),

If any migrations between the two fail (so a particular table doesn't exist or another migration was not run), it fails silently.

Jul 24 16:14:30 lsa-spcfy1-d docker/s795-sb-specify7-sb-1[1439]: MySQLdb.OperationalError: (1050, "Table 'spmerging' already exists") Jul 24 16:14:30

Reported By: SAIAB, KU, UT Austin, Cal Academy