HDC 3A: support handling archival status updates #8605
Description
Overview of the Feature Request As part of Harvard Data Commons, there is a requirement to support an archival system reporting status back to Dataverse as an archiving process proceeds. Current archiving classes can only succeed or fail and the current mechanism only allows differentiation between success and not-started-or-failed. The accompanying PR adds support to handle various archival-system-defined Pending states and to differentiate failure from not-yet attempted (useful with #7493 for example to avoid reprocessing already failed dataset versions.) The PR adds the logic to store the status, to set it during the initial archiving call and for a superadmin (or system holding an API key from a superadmin account) to subsequently update the status. A subsequent issue/PR will provide a UI mechanism to display the current status to admins/privileged users.