Implement alternative solution for cleanup_archive_dir

Had to comment out this function call when adding Azure Mass compatibility as users of cdds are expected to only have read+write permissions but no delete.

Start by locating the cleanup_archive_dir function and reviewing how it is called in the Azure Mass compatibility path. Confirm the expected behavior for users with read and write permissions but no delete permission, then identify the relevant tests or add coverage for the alternative cleanup behavior.

Written by the indexing model from the issue text.