Fail asv workflows when performance deteriorates

Nessuno ha ancora preso questa issue.

Fail the ASV workflows if at least one of benchmarks deteriorates above a certain threshold (e.g. 150% / 200%).

**asv-main.yml**:
- Execute `asv run` without `|| true`, allowing the command to exit with a non-zero return code
- Submit benchmarks and deploy dashboard on gh-pages, if the previous command succeeded or not

**asv-pr.yml**:
- Execute `asv continuous` without `|| true`, allowing the command to exit with a non-zero return code
- Output the performance comment on the PR if the comparison was successful or not

**asv-nightly.yml**
- Execute `asv continuous` without `|| true`, allowing the command to exit with a non-zero return code
- Write the commit hash to cache, if the previous if the comparison was successful or not

More information about "on failure" executions [here](https://docs.github.com/en/actions/learn-github-actions/expressions#status-check-functions).

Iniziate da .github/workflows/asv-main.yml, asv-pr.yml e asv-nightly.yml e verificate come ciascuno gestisce attualmente gli errori di asv run o asv continuous. Aggiornate le condizioni di errore dei workflow mantenendo i passaggi richiesti di submit, dashboard, PR comment e cache, quindi verificate che i workflow continuino a eseguire tali passaggi quando i confronti falliscono.

Scritto dal modello di indicizzazione a partire dal testo della issue.