Batch Edit: Locality's `lat1text` and `lat2text` fields get updated internally and marks the record as updated

[sharadsw]

From @combs-a:

LatLon has been kind of fixed, but there are also potentially integers; ints are being converted to floats and that marks them as updated cells when they shouldn't be.

The fields lat1text and lat2text are updated internally through the workbench which means Locality records can get marked as updated even when there are no changes visible to the user. This could potentially cause issues with matching records in batch edit when relationships are enabled in #6126

More info here: #5417 (comment)

[CarolineDenis]

NOTES:

• Workbench has the same behavior
• Keep it as known behavior for now
  Relevant code is here:

specify7/specifyweb/specify/parse.py

This was added for CoGe tool, we might break it if we fix this.

[lexiclevenger]

As of 7.11, records affected by this are no longer highlighted as updated. Now, they're marked as new cells and a new record is created after committing the data set, resulting in duplicate locality records despite no changes actually being made by the user.

In this data set, I only edited row 5, but batch edit would create new records for localities I made no changes to.