Update start and end period in GeologicTimePeriod when reversed

[CarolineDenis]

Fixes #5412

Warning

This PR affects database migrations. See migration testing instructions.

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

Testing instructions

• Open a db with production that has geologic time period tree
• Open a node
• Find a node that has a start period greater than the start or create one or update one => start 100 - end 200
• Save
• Change the branch to use this pr and not prod
• Open the node from the previous step
• Verify the start period is now greater than the end. start 200 - end 100

[pashiav]

• Verify the start period is now greater than the end. start 200 - end 100

---

Looks good! Start periods are greater than the end period.

[grantfitzsimmons]

To clarify, this does not follow this request in the original issue:

if the user has not modified the defaults in any way.

That means all chronostratigraphic records will now switch the values, so the startPeriod value should be larger than the endPeriod value. This does not consider if the defaults have or have not been modified.

Do we understand why the chronostrat tree was initially set up as it was? Are we comfortable updating user-created data without notifying anyone?

[alesan99]

• Verify the start period is now greater than the end. start 200 - end 100

---

I agree with Grant since it did change some of the chronostrat records I added myself, but functionality wise it worked without issue.

Left: New
Right: Old

Values have been updated correctly 👍

[grantfitzsimmons]

TODO: Add to release notes 👍