Add auditing of what method was used for data imports, updates, deletes

[XingY]

Rationale

This pull request adds audit tracking capabilities for data modification operations by introducing an EDIT_METHOD enum and integrating it into query API functions. The changes enable tracking of how data was modified (e.g., bulk edit, detail edit, grid edit) along with the request source location.

Related Pull Requests

• Add auditing of what method was used for data imports, updates, deletes labkey-api-js#200
• Add auditing of what method was used for data imports, updates, deletes #1874
• https://github.com/LabKey/labkey-ui-premium/pull/838
• Add auditing of what method was used for data imports, updates, deletes platform#7145
• https://github.com/LabKey/limsModules/pull/1753
• Add auditing of what method was used for data imports, updates, deletes commonAssays#944
• https://github.com/LabKey/premiumModules/pull/391
• Add test for transaction audit details testAutomation#2763

Changes

• Introduced EDIT_METHOD enum to categorize different types of data modifications
• Modified api.query.insertRows/updateRows/deleteRows/saveRows and moveEntities to accept and process editMethod parameter and record request hash in 'requestSource`
• Moved updateRowFieldValue out of ui-components since it's not used here