WorkBench and BatchEdit create update and delete operations for Data Sets are not Audit Logged

[melton-jason]

Describe the bug
Create, Update, and Delete operations with WorkBench and BatchEdit Data Sets are not Audit Logged.

To Reproduce
Steps to reproduce the behavior:

1. Create a WorkBench and/or BatchEdit Data Set
2. Rename the Data Set
3. Delete the Data Set
4. Check the Audit Log and see that all of the above operations are not logged

Expected behavior
Specify should log when a Data Set is created, modified, and deleted.

Please fill out the following information manually:

• OS: macOS Tahoe 26.3.1 (a)
• Browser: Chrome 151.0.7922.174 (Official Build) (arm64)
• Specify 7 Version: v7.12.0.7

Reported By
Discovered by investigation into #8434

Additional context
The following SQL Query can be used to export the most recent 200 Audit Logs, in order of most recent to least recent:

SELECT log.SpAuditLogID, log.Action, log.ParentRecordId, log.ParentTableNum, log.RecordId, log.TableNum, field.FieldName, field.NewValue, field.OldValue, log.TimestampCreated FROM spauditlog log LEFT OUTER JOIN spauditlogfield field ON log.SpAuditLogID=field.SpAuditLogID ORDER BY spauditlogid DESC LIMIT 200;

You can additionally use the QueryBuilder to view the Audit Log: https://speciforum.org/t/querying-the-audit-log/1878

[melton-jason]

Some further background in case it might prove beneficial in the future:

The actual NULL/empty result is coming from the following, where no match is found for the tree record with "seemingly" empty/incomplete ranks:

specify7/specifyweb/backend/workbench/upload/treerecord.py

Lines 609 to 612 in 1ea8aed

	if not tdiwprs:
	columns = [pr.column for prs in self.parsedFields.values() for pr in prs]
	info = ReportInfo(tableName=self.name, columns=columns, treeInfo=None)
	return (UploadResult(NullRecord(info), {}, {}), [], {})

The NULL value was being "unpacked" from the UploadResult by the following within the Determination's (or any table which had a relationship to a tree table) BoundUpdateTable:

specify7/specifyweb/backend/workbench/upload/upload_table.py

Lines 1026 to 1029 in 1ea8aed

	to_one_ids = {
	model._meta.get_field(fieldname).attname: result.get_id()
	for fieldname, result in to_one_results.items()
	}

specify7/specifyweb/backend/workbench/upload/upload_result.py

Lines 413 to 414 in 1ea8aed

	def get_id(self) -> int | None | Failure:
	return self.record_result.get_id()

specify7/specifyweb/backend/workbench/upload/upload_result.py

Lines 182 to 183 in 1ea8aed

	def get_id(self) -> None:
	return None

Thus when considering and applying changes to the record, BatchEdit would overwrite whatever existing value there was for the tree relationship with None/NULL:

specify7/specifyweb/backend/workbench/upload/upload_table.py

Lines 1125 to 1135 in 1ea8aed

	def _do_update(self, reference_obj, dirty_fields, **attrs):
	# TODO: Try handling parent_obj. Quite complicated and ugly.
	self.auditor.update(reference_obj, None, dirty_fields)
	for key, value in attrs.items():
	setattr(reference_obj, key, value)
	if hasattr(reference_obj, "version"):
	# Consider using bump_version here.
	# I'm not doing it for performance reasons -- we already checked our version at this point, and have a lock, so can just increment the version.
	setattr(reference_obj, "version", getattr(reference_obj, "version") + 1)
	reference_obj.save()
	return reference_obj