Support for AIP updates when ingesting SIP that refer existing AIPs

[jmaferreira]

The use case is as follows:

Sometimes it is useful to resubmit a particular SIP that will replace the information placed before in a given AIP or update the representations of that AIP with additional files. For that, a repository should receive a SIP with the status UPDATE that identifies the AIP or the ID of the previous SIP submitted. The repository should be able to understand that it is an AIP UPDATE request by looking at the SIP status and identify the AIP to which the update should be performed.

In order to support this feature, the AIP spec should be updated to describe what should happen at the AIP level if an update is received via the ingest process.

@luis100 may be consulted to provide more details on current implementations.

This issue is related to DILCISBoard/E-ARK-SIP#6

[karinbredenberg]

Following the decision at the DILCIS Board meeting on the 6th of February a working group is going to be created.
See: https://github.com/DILCISBoard/GroupDocumentation/blob/master/MeetingNotes/2024/20240206%20DILCIS%20Board%20and%20EARK%20CSP%20CORE11%20and%20others.md