Create a configuration tool

[CarolineDenis]

Fixes #6213

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

Notes: Taxon will be created for a discipline in the tree viewer not in the config tool / tree config will be added and evaluated once this pr and the tree default creation are merged in the setup pr

General

• Open the System Config Tool (available from the User Tools menu).

Hierarchy Display

• Verify that existing Institutions → Divisions → Disciplines → Collections are displayed in the left hierarchy tree.
• Verify that each section in the left hierarchy tree can be expanded and collapsed.
• Verify that existing Institutions → Divisions → Disciplines → Collections are displayed in the right tree visualization.
• Verify that the orientation of the right tree visualization can be switched between horizontal and vertical.
• Verify that clicking Edit next to any resource in the left hierarchy tree opens a dialog with the resource details.
• Verify that clicking any resource in the right tree visualization opens a dialog with the resource details.

---

New Resource Creation

• Click Add {resource name} (Division, Discipline, or Collection).

• Fill in the form.

  • Note: For Disciplines, the Type field must currently be entered manually in this PR.
    The pick list is implemented in a separate PR:
    https://github.com/specify/specify7/pull/7584/files
  • Note: Discipline creation may timeout. The discipline will still be created after waiting a while. This is expected behavior for now, and will be addressed in Speed up schema config creation (and general refactoring) #7615

• Click Save.

---

Edit Function

• Verify that newly created resources appear in both hierarchy trees.
• Verify that you can edit an existing resource and successfully save the changes.

---

Delete Function

• Verify that a resource cannot be deleted if it is in use
  (e.g., a Discipline containing a Collection with data).

• Verify that a resource can be deleted if it is not in use
  (e.g., a Discipline with only empty Collections).

  • Deleting a Discipline should also delete its empty Collections.

[CarolineDenis]

• Add a migration to create a pick list for discipline type field.

Discipline section:
For geography rank configuration, taxon rank configuration, and tree creation:
After adding a new discipline, the page will reload and the discipline will appear in the hierarchy display. Next to the new discipline, two icons will be shown: a globe and a tree. A red warning message will also appear, prompting the user to configure both the taxon tree and the geography tree. The globe icon is conditional—if the geography tree is set to global, it will not be displayed.
When the user clicks on either the tree or globe icon, a dialog will open containing the corresponding rank configuration form. Once both configurations are saved, a “+” icon will appear next to the discipline, allowing the user to add a new collection.

[alesan99]

• Verify that existing Institutions → Divisions → Disciplines → Collections are displayed in the left hierarchy tree.
• Verify that each section in the left hierarchy tree can be expanded and collapsed.
• Verify that existing Institutions → Divisions → Disciplines → Collections are displayed in the right tree visualization.
• Verify that the orientation of the right tree visualization can be switched between horizontal and vertical.
• Verify that clicking Edit next to any resource in the left hierarchy tree opens a dialog with the resource details.
• Verify that clicking any resource in the right tree visualization opens a dialog with the resource details.
• Verify that the right tree visualization supports scrolling vertically and horizontally.
• Verify that newly created resources appear in both hierarchy trees.
• Verify that you can edit an existing resource and successfully save the changes.
• Verify that a resource cannot be deleted if it is in use
• Verify that a resource can be deleted if it is not in use

---

Everything works 👍

The resources are also being updated without having to clear the cache as well.,

Tree creation for new disciplines doesn't entirely work correctly in this PR, but that's only because the Setup PR #6671 still needs improvements with tree creation.

[grantfitzsimmons]

General

• Open the System Config Tool (available from the User Tools menu).

Hierarchy Display

• Verify that existing Institutions → Divisions → Disciplines → Collections are displayed in the left hierarchy tree.
• Verify that each section in the left hierarchy tree can be expanded and collapsed.
• Verify that existing Institutions → Divisions → Disciplines → Collections are displayed in the right tree visualization.
• Verify that the orientation of the right tree visualization can be switched between horizontal and vertical.
• Verify that clicking Edit next to any resource in the left hierarchy tree opens a dialog with the resource details.
• Verify that clicking any resource in the right tree visualization opens a dialog with the resource details.

---

New Resource Creation

• Click Add {resource name} (Division, Discipline, or Collection).

• Fill in the form.

  • Note: For Disciplines, the Type field must currently be entered manually in this PR.
    The pick list is implemented in a separate PR:
    https://github.com/specify/specify7/pull/7584/files

• Click Save.

I had some trouble here. I created a new Discipline and Collection under an existing Division:

The new collection is "Example Insect Collection". I can switch to it, log in, but the schema doesn't exist.

• Navigating to the Schema Config and selecting a table (e.g. Preparation), I get the following error: Error: Unable to find SpLocaleContainer for Preparation

Some resources seem to have been created correctly based on my discipline– for example, preptype records:

Strangely, when I go to the 'Taxon' tree, I see an 'Animalia' node. Not relevant to insects and I would expect "Life" to be the only node:

It is correctly fetching the default forms for the insect discipline.

---

Edit Function

• Verify that newly created resources appear in both hierarchy trees.
• Verify that you can edit an existing resource and successfully save the changes.

Even in cases where the changes are made to the forms of the resources, it does fetch the changes immediately. Looks good!

---

Delete Function

• Verify that a resource cannot be deleted if it is in use
  (e.g., a Discipline containing a Collection with data).
• Verify that a resource can be deleted if it is not in use
• Deleting a Discipline should also delete its empty Collections.

[alesan99]

The new collection is "Example Insect Collection". I can switch to it, log in, but the schema doesn't exist.

This should be fixed now 👍
Since schema config creation takes a while you may now get a timeout error though, but that would be solved by schema config speedups described in this issue: #7615

Strangely, when I go to the 'Taxon' tree, I see an 'Animalia' node. Not relevant to insects and I would expect "Life" to be the only node:

Any tree issues will be sorted once #7593 combines the functionality of the default tree creation PR and the setup PR.