Generate docs for all tag pushes

[Eric-Arellano]

Summary

The docs team needs to generate the docs for 2.4.0rc2, but there was no Sphinx artifact created. In the past, I would manually trigger a workflow, but that isn't sustainable and the team taking over API release docs generation does not have write permission to Qiskit/qiskit.

Details and comments

This simply runs on all tags. This workflow only uploads the asset to GH Artifacts, whereas it used to update qiskit.org directly. So, running this workflow more than strictly necessary is extremely low risk.

(Technically, we need ** if we want to run on tags that include /.)

[qiskit-bot]

One or more of the following people are relevant to this code:

• @Qiskit/terra-core

[Eric-Arellano]

It would help to please manually trigger a run of https://github.com/Qiskit/qiskit/actions/workflows/docs_deploy.yml for the recent 2.4.0rc2, then ping @Qiskit/docs-content-team once it is ready for them to generate the docs.

[jakelishman]

Seems like we've had it like this ever since it was first introduced in #10610, back when this pipeline actually deployed direct to qiskit.org (RIP).

tbh, at this point we can probably just fold the logic into the regular docs job - it's not like either of them push the artifact anywhere.

If you don't care about the version number being set in QISKIT_DOCS_GITHUB_BRANCH_NAME during the env, then you can get the artifact from https://github.com/Qiskit/qiskit/actions/runs/23614935461 (direct link: https://github.com/Qiskit/qiskit/actions/runs/23614935461/artifacts/6131879851). If not, I can manually trigger it tomorrow if you like, or you can just wait til we make a 2.4.0rc3.

[Eric-Arellano]

Manual trigger would be great. Thanks! We've been trying to stress test the documentation we left behind for generating API docs, which includes how to find the GH artifact.