Prepare second docs artifact, for human consumption

[garrison]

This is what it would look like if we were to generate a second docs artifact, meant for human consumption. The reason we might want to do this because some of us (me) will be more likely to download and look at a docs preview if the artifact is nicer to work with. The reason we might not want to do this is because it adds lines to our CI configuration.

Follow-up to #5 (comment) and #8.

---

UPDATE: actually, after trying to work with the github-pages artifact, I am much in favor of this. Working with that one basically involves

mkdir /tmp/newdir
cd /tmp/newdir
unzip '~/Downloads/github-pages (39).zip'
tar xf artifact.tar

while this artifact for humans can be extracted easily anywhere using unzip without causing much harm (everything in a single subdirectory with the same name).

[coveralls]

Pull Request Test Coverage Report for Build 10777419036

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 10770310602:	0.0%
Covered Lines:	297
Relevant Lines:	297

---

💛 - Coveralls

[mrossinek]

Is this really needed? You can just as easily get the github-pages artifact from the actions tab, for example: https://github.com/Qiskit/qiskit-addon-utils/actions/runs/10770310597

[garrison]

Is this really needed? You can just as easily get the github-pages artifact from the actions tab, for example.

I mentioned this in the update, above. You might not have seen that if you read only the email notification.

That artifact has a generic name and extracts into a tar file which then can be extracted into the current directory. The artifact for humans has an intentional name and extracts into a subdirectory. It's meant to be more convenient to work with.

[mrossinek]

I indeed overlooked your updated description.

I still do not see a pressing need for this, but it does not harm 👍