Make update path verification a blocking step in monthly release pipeline

Context

In #21059 (closed), we add the update path QA as a new job in the release pipelines (monthly+patch). To make sure we can test running it without breaking the release pipelines, allow_failure: true is set on the jobs (e.g. security_release_verify_update_path and security_release_verify_update_path:create_dynamic_pipeline ).

Once we are confident that the QA jobs work well, we can officially use it in the place of the release instance verification in the release pipelines.

Prerequisite

• monthly_release_verify_update_path runs successfully in one monthly release pipeline

Exit Criteria

• allow_failure: true is removed from the update path jobs in the monthly release pipeline

• Remove the step in the release issue template:

  • This step is optional at the moment. Ignore and continue the release process if this step fail.