GitHub Issue 903: Remove Cross-Container Sample and Data Class Import Feature

[XingY]

Rationale

This PR removes the support for cross-container sample and data class import feature. The feature allowed import of samples and data class rows belonging to other folders in a single file, which was implemented via temp partitioned files, which is error-prone. Attempts to update/merge rows that does not exist in the current container now generate a generic error message ("Sample/Data does not exist in : "), without revealing its existence in other folders.

Related Pull Requests

• GitHub Issue 903: Remove Cross-Container Sample and Data Class Import Feature labkey-ui-components#2007
• https://github.com/LabKey/labkey-ui-premium/pull/956
• GitHub Issue 903: Remove Cross-Container Sample and Data Class Import Feature testAutomation#3017
• GitHub Issue 903: Remove Cross-Container Sample and Data Class Import Feature #7698
• https://github.com/LabKey/limsModules/pull/2221

Changes

• Fixed issue that orphaned exp.material record is created when merging a sample in a container that user lacks read permission to
• Remove crossFolderImport from DataIteratorContext and AbstractQueryImportAction.Params
• Remove stale QueryUpdateService.hasExistingRowsInOtherContainers
• Remove DefaultQueryUpdateService.configureCrossFolderImport
• Remove cross-folder partitioning, folder-column detection, and per-container split-file logic from MultiDataTypeCrossProjectDataIterator
• Container/Folder columns are now always dropped during sample and data class import (previously they were conditionally kept for cross-folder merges)
• SampleTypeUpdateServiceDI.getExistingRows: use ElevatedUser when searching other containers for cross-container existence checks, so samples are not missed due to the requesting user's limited read permissions
• ExpDataClassDataTableImpl._select: add ClassId to the RowId filter to avoid returning a row from a different data class with the same RowId; add fallback lookup against exp.data when allowCrossContainer is true to account for data filtered out due to user's permission
• Standardize "not found" error messages across samples and data classes for data present in an folder without permission and data don't exist anywhere