Add settings retry attempts and interval retry attempts for recurring snapshots

### The required feature described as a wish

We are facing a problem with recurring snapshots for volumes. When a recurring snapshot job fails, ACS keeps making endless retry attempts.

The user does not receive any notifications when a recurring snapshot job fails. Only repeated retry attempts to create the snapshot are observed.

In our test case, we reproduced the issue with an error:
```
Error while creating entity for allocating snapshot
```

It would be good to have the ability to configure:
- the of retry attempts
- the interval between retries

To avoid an infinite snapshot creation loop that ends with an error. After the maximum number of retries is exhausted, a notification should be sent informing that the job has failed.

Related discussion: [Recurring snapshots: How to limit retry attempts or configure interval in global settings? #13439 ](https://github.com/apache/cloudstack/discussions/13439)

Aucun fichier ni test n’est identifié dans l’issue. Commencez par retracer le job récurrent de snapshot ainsi que ses chemins existants de nouvelle tentative et de notification, puis identifiez les points d’entrée de la configuration ; le travail est considéré comme terminé lorsque des nouvelles tentatives limitées et configurables, un intervalle entre les nouvelles tentatives et une notification d’échec après épuisement sont en place.

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