Ask for confirmation before all destructive operations

[pcdavid]

Problem

Some operations like deleting a representation or an element (and all its descendants) from the explorer are destructive, but currently they do not ask for confirmation before.
Deleting a whole document does ask for confirmation, but there is no particular reason to treat documents differently from e.g. the root elements inside of them (deleting them is as impacting as deleting the document).

Solution

Make the confirmation dialog available on all concepts of the explorer (objects, representations, etc)

Rabbit holes

No-gos

• A large set of validation rules for specific DSLs
• Dynamic contributions of additional validation rules.

Test

• Automated developer tests merged and pass (with reasonable code coverage)
• Automated End-to-End tests merged and pass (Cypress)
• Feature/bug fix manually tested/validated by at least one person not involved in the implementation
• Collaborative tests passed by hand
• Exploratory test passed by MEB
• Business acceptance test passed by MEB

Doc

• Internal Doc updated
• External Doc updated
• Validation Doc updated

UX/UI

• Zeroheight updated
• Storybook updated

Next

• Any left-over tasks added to the issues on Github

[sbegaudeau]

I'm removing it from the 0.4.0 milestone since it may arrived in this milestone but it's not sure for the moment.

[pcdavid]

As part of #692 which generalizes the treatment of explorer items, the DeleteDocumentModal is/will be removed as it was too specific to the document type to match the new generic behavior.

I think now would be the right time to introduce a generic deletion confirmation modal and use it for relevant operations from the explorer:

• document removal;
• item removal;
• representation removal (Slightly less critical, the most you can lose at the moment is a custom layout. Other that than you can always recreate a structurally equivalent representation.)

[pcdavid]

See #3089 which covers this.