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)

En el issue no se identifican archivos ni pruebas. Empieza siguiendo el job recurrente de snapshot y sus rutas existentes de reintento y notificación, y después identifica los puntos de entrada de configuración; se considera terminado cuando haya reintentos acotados y configurables, un intervalo entre reintentos y una notificación de fallo tras agotarlos.

Escrito por el modelo de indexación a partir del texto del issue.