Reimplement timestamp logic

[realVinayak]

Fixes #5108

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

Testing instructions

[grantfitzsimmons]

This must be tested:

---

Expected Behavior:

• When a column within a specified table is linked to either timestampModified or timestampCreated, it should not be automatically replaced upon uploading new data.
• In cases where a column is not associated with timestampModified or timestampCreated, the system should autonomously allocate both fields with the current timestamp.
• When new records are generated in other tables during the same upload process, if no column is directly linked to timestampModified or timestampCreated, the system should automatically assign both fields with the current timestamp.
• timestampModified or timestampCreated should be assigned the current timestamp in all cases during WorkBench uploads except when a column is mapped to that field where that row contains a value

[realVinayak]

we also don't need

specify7/requirements.txt

Line 12 in c3d0ab1

django-model-utils==4.4.0

anymore, @acwhite211

[emenslin]

Expected Behavior:

• When a column within a specified table is linked to either timestampModified or timestampCreated, it should not be automatically replaced upon uploading new data.
• In cases where a column is not associated with timestampModified or timestampCreated, the system should autonomously allocate both fields with the current timestamp.
• When new records are generated in other tables during the same upload process, if no column is directly linked to timestampModified or timestampCreated, the system should automatically assign both fields with the current timestamp.
• timestampModified or timestampCreated should be assigned the current timestamp in all cases during WorkBench uploads except when a column is mapped to that field where that row contains a valu

I worked mostly with the CO table and the Agents table and everything looks good. All cases mentioned in the expected behavior work and the timestamp modified field is now updated when a record is edited.

[acwhite211]

we also don't need

specify7/requirements.txt

Line 12 in c3d0ab1

django-model-utils==4.4.0

anymore

Ya, since we're not using the FieldTracker anymore for tracking changes in the timestamp fields, we can remove this requirement.

[alesan99]

• When a column within a specified table is linked to either timestampModified or timestampCreated, it should not be automatically replaced upon uploading new data.
• In cases where a column is not associated with timestampModified or timestampCreated, the system should autonomously allocate both fields with the current timestamp.
• When new records are generated in other tables during the same upload process, if no column is directly linked to timestampModified or timestampCreated, the system should automatically assign both fields with the current timestamp.
• timestampModified or timestampCreated should be assigned the current timestamp in all cases during WorkBench uploads except when a column is mapped to that field where that row contains a valu

I can confirm timestamps are being updated again for collection objects 👍 I uploaded the same data I did when comparing to edge.
The timestamps are also filled in accordingly when there is no corresponding columns.

[Areyes42]

• When a column within a specified table is linked to either timestampModified or timestampCreated, it should not be automatically replaced upon uploading new data.
• In cases where a column is not associated with timestampModified or timestampCreated, the system should autonomously allocate both fields with the current timestamp.
• When new records are generated in other tables during the same upload process, if no column is directly linked to timestampModified or timestampCreated, the system should automatically assign both fields with the current timestamp.
• timestampModified or timestampCreated should be assigned the current timestamp in all cases during WorkBench uploads except when a column is mapped to that field where that row contains a value

---

I tested on COs, agent, and locality tables, and it looks like all the timestamps are now properly updated compared to the behavior in edge 👌

[lexiclevenger]

Expected Behavior:

• When a column within a specified table is linked to either timestampModified or timestampCreated, it should not be automatically replaced upon uploading new data.
• In cases where a column is not associated with timestampModified or timestampCreated, the system should autonomously allocate both fields with the current timestamp.
• When new records are generated in other tables during the same upload process, if no column is directly linked to timestampModified or timestampCreated, the system should automatically assign both fields with the current timestamp.
• timestampModified or timestampCreated should be assigned the current timestamp in all cases during WorkBench uploads except when a column is mapped to that field where that row contains a value

---

Looks good! Timestampmodified is also updated again when a record is modified through the data entry form.

[melton-jason]

Looks solid!