Fail asv workflows when performance deteriorates

還沒有人認領這個 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).

從 .github/workflows/asv-main.yml、asv-pr.yml 和 asv-nightly.yml 開始，檢查每個檔案目前如何處理 asv run 或 asv continuous 失敗。更新工作流程失敗條件，同時保留所要求的 submit、dashboard、PR comment 和 cache 步驟，然後驗證比較失敗時工作流程仍會執行這些步驟。

由索引模型根據 Issue 內容生成。