Prevent accidental deleting

https://ombulabs.atlassian.net/browse/DT-251

**IMPORTANT: please make sure you ask yourself all intro questions and fill all sections of the template.**

**Before we start...:**

- [x] I checked the documentation and didn't find this feature
- [x] I checked to make sure that this feature has not already been requested

**Branch/Commit:**

main

**Describe the feature:**

Please include a detailed description of the feature you are requesting and any detail on it’s expected behavior.

> **As a user**
> **I add a project that I which to use as some sort of template project**
> **And then I add all the stories with descriptions**
> **I don't want anyone to accidentally delete the template project (since it cannot be recovered)**
> **I don't want anyone to accidentally delete a story in my template project (since it cannot be recovered**

**Problem:**

Please include a detailed description of the problem this feature would solve.

> **As a user**
> **I add a project with stories**
> **So that I can use the project as a template to be cloned for future projects**
> **Now I or anybody on my team can delete the project**
> **And I or anybody on my team can delete stories in the project**
> **There is no way to prevent projects or stories from being deleted**
> **There is no way to recover a project or story after it has been deleted**

**Ideas:**

I see two possible solutions, we can discuss implementing either or both.

1. A permission scheme that prevents unauthorised deletion.
2. Prevent deleting all together, use a different mechanism such as archiving or rejecting
3. Allow soft deleting only so we can recover projects and stories.

**I will abide by the [code of conduct](https://github.com/fastruby/points/blob/main/CODE_OF_CONDUCT.md)**

L’issue ne mentionne aucun fichier, test ni point d’entrée. Déterminez d’abord si le projet a besoin d’autorisations de suppression, d’archivage, de soft deletion ou d’une combinaison de ces mécanismes, puis retracez les flux existants de suppression des projets et des stories. Le travail est considéré comme terminé lorsque l’approche sélectionnée empêche les suppressions accidentelles ou permet de les récupérer, et qu’elle est vérifiée à la fois pour les projets et les stories.

Rédigé par le modèle d'indexation à partir du texte de l'issue.