Add support for viewing current migration status from the UI

[grantfitzsimmons]

We need to manually query on the django_migrations table to find the status, or enter into the Specify 7 container via command line and run

specify@ec8f80d05fd2:/opt/specify7$ ve/bin/python manage.py showmigrations
accounts
 [X] 0001_initial
 [X] 0002_auto_20211223_1206
 [X] 0003_auto_20220621_1541
attachment_gw
 [X] 0001_initial
auth
 [X] 0001_initial
 [X] 0002_alter_permission_name_max_length
 [X] 0003_alter_user_email_max_length
 [X] 0004_alter_user_username_opts
 [X] 0005_alter_user_last_login_null
 [X] 0006_require_contenttypes_0002
 [X] 0007_alter_validators_add_error_messages
 [X] 0008_alter_user_username_max_length
 [X] 0009_alter_user_last_name_max_length
 [X] 0010_alter_group_name_max_length
 [X] 0011_update_proxy_permissions
 [X] 0012_alter_user_first_name_max_length
businessrules
 [X] 0001_initial
 [X] 0002_default_unique_rules
 [X] 0003_catnum_constraint
 [X] 0004_catnum_uniquerule
 [X] 0005_cojo
 [X] 0006_storage_uniqueIdentifier
 [X] 0007_more_uniqueness_rules
contenttypes
 [X] 0001_initial
 [X] 0002_remove_content_type_name
notifications
 [X] 0001_initial
 [X] 0002_message_read
 [X] 0003_spmerging
 [X] 0004_rename_merge_policy
 [X] 0005_auto_20240530_1512
 [X] 0006_localityupdate_localityupdaterowresult
patches
 [X] 0001_restore_separators
 [X] 0002_fix_accepted_taxon
 [X] 0003_coordinate_fields_fix
permissions
 [X] 0001_initial
 [X] 0002_role_rolepolicy_userrole
 [X] 0003_auto_20220321_1445
 [X] 0004_intialize_defaults
 [X] 0004_auto_20220407_1927
 [X] 0005_merge_20220414_1451
 [X] 0006_add_dataset_create_recordset_permission
 [X] 0007_add_stats_edit_permission
 [X] 0008_attachment_import_role
sessions
 [X] 0001_initial
specify
 [X] 0001_initial
 [X] 0002_geo
 [X] 0003_cotype_picklist
 [X] 0004_stratigraphy_age
 [X] 0005_collectionobjectgroup_parentcojo
 [X] 0006_fix_tectonic_tree_fields
 [X] 0007_schema_config_update
 [X] 0008_ageCitations_fix
 [X] 0009_tectonic_ranks
 [X] 0010_updateDelete_parentcojo
 [X] 0011_cascading_tree_nodes
 [X] 0012_add_cojo_to_schema_config
 [X] 0013_collectionobjectgroup_parentcog
 [X] 0014_spqueryfield_strict
 [X] 0015_add_version_to_ages
 [X] 0016_collectionobjecttype_catalognumformatname
 [X] 0017_schemaconfig_fixes
 [X] 0018_cot_catnum_schema
 [X] 0019_remove_parentCog
 [X] 0020_add_tectonicunit_to_pc_in_schema_config
 [X] 0021_update_hidden_geo_tables
 [X] 0022_ensure_default_cots
 [X] 0023_update_schema_config_text
 [X] 0024_add_uniqueIdentifier_storage
 [X] 0025_alter_collectionobjectgroupjoin_childco
 [X] 0026_taxontreedef_alter_delete
 [X] 0027_CO_children
 [X] 0028_selectseries
 [X] 0029_remove_collectionobject_parentco
 [X] 0030_fix_storage_uniqueidentifier
 [X] 0031_add_default_for_selectseries
 [X] 0032_remove_spquery_selectseries
workbench
 [X] 0001_initial
 [X] 0002_spdataset_visualorder
 [X] 0003_auto_20210218_1256
 [X] 0004_auto_20210219_1131
 [X] 0005_auto_20210428_1634
 [X] 0006_batch_edit
 [X] 0007_spdatasetattachment
 [X] 0008_spdataset_rolledback

[realVinayak]

That's an interesting idea. I think it can help beyond test panel. Maybe an end-point can be added to specify7 that lists all the migrations done, like there is for system info (so, devs and help staff can check migration status from browser). Just being able to access migration status from systm info will also be faster than backend route?

Even better for UI, the django_migrations table can be added to datamodel (but not Django models). That way, query builder will be able to pick it up. Since Django model won't be added, the risk of people modifying the django_migrations table is mitigated.

I think the test panel can then sit on top of the API (so, it'll just aggregate results).