generate-docs: Use ubuntu-latest

[awelzel]

Commit bd30042 removed the sudo usage
which was the actual culprit for using the wrong pip version. Bump up
to ubuntu-latest again.

[awelzel]

@bbannier - see anything wrong with this? It's a follow-up to #280 based on the comment I made there. I'll update the commit to be a bit more descriptive if you think this is good.

[bbannier]

@bbannier - see anything wrong with this? It's a follow-up to #280 based on the comment I made there. I'll update the commit to be a bit more descriptive if you think this is good.

Not really sure how this failed before when we were already using actions/setup-python and were also setting python-version; AFAICT this should never have exposed us to issues from the base image (actions/runner-images#10636), but it did. By using an unpinned image we allow GH to break us again, and I do don't think we get much benefit from defaulting to the latest image beyond not having to worry about that image being retired.

[awelzel]

Not really sure how this failed before when we were already using actions/setup-python and were als setting python-version

Pretty sure that because of the sudo usage it would reset PATH and use the system pip rather than pip provided by setup-python. So I think the right fix was to remove the sudo.

[bbannier]

Not really sure how this failed before when we were already using actions/setup-python and were als setting python-version

Pretty sure that because of the sudo usage it would reset PATH and use the system pip rather than pip provided by setup-python. So I think the right fix was to remove the sudo.

🤦.

Still not fully convinced of the benefit of "latest", but I guess it now might hurt less.

Do you have an idea why we need to "test" this against so many different versions? With your explanation it might not have tested much before anyway, and I also do not understand why we would care at all as long as we can build on RTD and with our minimum supported version (if at all).