[Docs] Use contracts for removing sheets

[HLWeil]

Currently, the Update contracts are designed in a way to minimize user information loss.

The reasoning is as follows:
-> The datamodel does not represent every information stored in the filesystem (Like styling in xlsx files).
-> So when the user makes some changes to the assay portion of the datamodel and updates their filessystem, not the whole assay file should be overwritten
-> Instead, only those portions specified in the new spreadsheet should be updated (namely the annotation tables)

But what happens, when the user deletes parts in the datamodel that are equivalent to one sheet in the assayfile (e.g. the growth protocol)? Somehow this deletion should also happen in the filesystem, otherwise the user will be surprised to find this annotation table again in the datamodel next time they read the arc.

---

One possible solution: Make it a rule to delete all annotationTables that are not included in the updated spreadsheet.

[HLWeil]

Removed duplicate issue #122

@Freymaurer:

Related: fslaborg/FsSpreadsheet#30

We need to update only ISA changes, without touching any other user content. Therefore we must establish a system to handle this.

For UPDATE contracts we MUST pass all Tables and the metadata sheet. Any table not passed MUST be deleted, any table passed MUST be updated if changed. The metadata sheet passed MUST be updated if changed.

The exact replacement/update of tables MUST be handled/implemented by the specific IO arctrl implementation.

[Freymaurer]

This will postponed into the future.