Discipline type picklist in migration

[alesan99]

Fixes #7582

Warning

This PR affects database migrations. See migration testing instructions.
⚠️

Adds a new discipline types picklist.

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

• Go to schema config -> Discipline
• Make sure the type field is set to the new Discipline Types picklist
• Make sure the picklist has all the discipline proper types
• Dev Testing:
• Run specify 0042_discipline_type_picklist migration
• Revert the migration. Make sure the picklist was actually deleted.

[emenslin]

• Make sure the type field is set to the new Discipline Types picklist
• Make sure the picklist has all the discipline proper types

There is no discipline type picklist so the field is also not set to a picklist. I did also briefly get a migration error upon first load but it went away and I cannot reproduce it so I am not sure if it's a problem or not.

[alesan99]

There is no discipline type picklist so the field is also not set to a picklist. I did also briefly get a migration error upon first load but it went away and I cannot reproduce it so I am not sure if it's a problem or not.

@emenslin Hm I tried a copy of your database locally and the picklist migration ran. I'm not sure what a happened.

I did make changes to the code so hopefully it works now.

EDIT:
After trying it on the test panel I believe the issue is related to #7587

Once that PR is merged the migration should run.

[alesan99]

@specify/ux-testing with #7587 merged, this PR is ready to test again! 👍

[emenslin]

• Make sure the type field is set to the new Discipline Types picklist
• Make sure the picklist has all the discipline proper types

I'm still running into the same issue I mentioned above, there is no Discipline Type picklist, however, I did not run into any migration errors this time.