Design a flow for deleting boefje variants

[RomijnHumanoids]

Apart from making and approving variants, there also needs to be a flow for deleting a created boefje variant. Implementation Implementation ticket #3469 is already made but there is no design yet.

• Boefje variants can be deleted by an admin or by the user that created the variant.
• Users across multiple openKAT installs and organisations that enabled the variant need to be notified when a boefje is deleted and will not be scanning from that moment on.

[RomijnHumanoids]

FOR REVIEW: https://www.figma.com/design/wTD4hfTbZMp0o2G6VmUepU/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Boefjes?node-id=2728-25024&t=rbhtjEdhDk67uytj-1

[RomijnHumanoids]

For review with some small changes: https://www.figma.com/design/wTD4hfTbZMp0o2G6VmUepU/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Boefjes?node-id=2728-25024&t=jPCsPx5JLOUB4rn4-1

• ‘Delete plugin’ directly available at boefje variant.
• New design of boefje detail page features a tab for creator/admin control, including a delete plugin button.
• The deletion flow is the same for admin as boefje creator.

[RomijnHumanoids]

For review (sept. 18): https://www.figma.com/design/wTD4hfTbZMp0o2G6VmUepU/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Boefjes?node-id=2728-25024&t=Z6BgLedIjGAnRBKQ-1

Change log:

• The focus has shifted from letting users in other organisations ‘recover’ the deleted plugin to emphasising responsibility to admins to contact organisations that enabled the plugin.
• This is also limiting deletion possibilities for boefje creators in case other organisations have already enabled the plugin. If not, the creator is free to delete their creation.
• The different roles and how they will be notified in different situations is explained at the different modals.
• A new place to show list of organisations that enabled a not-yet-deleted plugin: the organisations tab on plugins (for admins)
• A new place to show list of organisations that enabled a deleted plugin: an archive tab in KAT-alogus.