Fix missing aggregation separators, add patches Django app

[grantfitzsimmons]

Warning

This PR affects database migrations. See migration testing instructions.

Fixes #5154, but retroactively, since this has already led to a lot of issues since the bug was introduced, and now its been insidiously spreading since (reported by numerous users, just solved another case today so I figured I should solve all of them at once).

This also creates a patches Django app that we can add to in the future when needing to do something like this.

It runs this on all databases:

UPDATE spappresourcedata spard
SET spard.data = REPLACE(spard.data, 'separator=""', 'separator="; "')
WHERE spard.SpAppResourceID IN (
    SELECT spar.SpAppResourceID
    FROM spappresource spar
    WHERE spar.Name = 'DataObjFormatters'
);

You cannot set the separator to nothing (""), so we can be very confident this solves cases where the default was lost and does not break cases where it is not desired.

Checklist

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

Testing instructions

Before using this branch, switch to v7.9.6.2 and edit the separator for any table aggregation.
Once you do, all default separators for table aggregations will be set to "" rather than "; ". This leads to very undesirable results where all Preparations or Collectors are aggregated together into a single string 😵

• Verify that all separators are cleared in v7.9.6.2 in a DataObjFormatters app resource

   <aggregators>
   	<aggregator name="AccessionAgent" title="AccessionAgent" class="edu.ku.brc.specify.datamodel.AccessionAgent" default="true" separator="" ending="" format="AccessionAgent"/>
   	<aggregator name="AccessionAttachment" title="AccessionAttachment" class="edu.ku.brc.specify.datamodel.AccessionAttachment" default="true" separator="" ending="" format="identity" orderfieldname="ordinal"/>
   	<aggregator name="AccessionAuthorization" title="AccessionAuthorization" class="edu.ku.brc.specify.datamodel.AccessionAuthorization" default="true" separator="" ending="" format="AccessionAuthorization"/>

• Pull this PR and run the migration

• Verify that all empty separators have been restored to default

   	<aggregators>
   		<aggregator name="AccessionAgent" title="AccessionAgent" class="edu.ku.brc.specify.datamodel.AccessionAgent" default="true" separator="; " ending="" format="AccessionAgent"/>
   		<aggregator name="AccessionAttachment" title="AccessionAttachment" class="edu.ku.brc.specify.datamodel.AccessionAttachment" default="true" separator="; " ending="" format="identity" orderfieldname="ordinal"/>
   		<aggregator name="AccessionAuthorization" title="AccessionAuthorization" class="edu.ku.brc.specify.datamodel.AccessionAuthorization" default="true" separator="; " ending="" format="AccessionAuthorization"/>
   		<aggregator name="Address" title="Address" class="edu.ku.brc.specify.datamodel.Address" default="true" separator="; " ending="" format="Address"/>
   		<aggregator name="AgentAttachment" title="AgentAttachment" class="edu.ku.brc.specify.datamodel.AgentAttachment" default="true" separator="; " ending="" format="identity" orderfieldname="ordinal"/>

[maxpatiiuk]

👍

[lexiclevenger]

• Verify that all separators are cleared in v7.9.6.2 in a DataObjFormatters app resource
• Pull this PR and run the migration
• Verify that all empty separators have been restored to default

---

Looks good! All empty separators are restored.

Before:

After:

---

This branch also makes aggregators appear in the visual editor menu that weren't previously hidden without enabling 'Show All Tables' (mostly Attachment tables). I think all of these tables have default aggregators, so it's probably not a problem unless they really need to be hidden.

Before:

After:

[specifysoftware]

This pull request has been mentioned on Specify Community Forum. There might be relevant details there:

https://discourse.specifysoftware.org/t/specify-7-10-2-release-announcement/2455/1