Add a retry step to the flaky part of our CI workflow

[kafitzgerald]

Add a retry step to the flaky part (creating the HTML) of our CI workflow

Partially addresses #562.

I only added the retry step in ci.yml and not in the upstream-dev CI, since that doesn't seem to have the same problem. I think it's the additional data downloads from multiple version/OS CI runs that are problematic here and this works as a bandaid of sorts.

I am also leaving the issue open since I think we should look into some sort of caching strategy to really address this. That might need to wait a moment though as I'm pretty swamped.

[kafitzgerald]

I spoke too soon on the lack of trouble with the upstream-dev-ci. That just failed last night for a similar reason.

I'll add a retry step on that as well.

[jukent]

I like this approach, we know if it is likely to time out sooner and can rerun it.

[jukent]

Want to see if the retry solves our problems here before applying it to upstream-ci?

[kafitzgerald]

Want to see if the retry solves our problems here before applying it to upstream-ci?

Should have referenced it, but I was testing on my fork and the flaky step does time out and the retry step works.

I can turn this on again and link to it when I add the upstream ci bit.

[kafitzgerald]

Here are the links to the test runs on my fork:

CI Upstream: https://github.com/kafitzgerald/geocat-examples/actions/runs/7492946925
CI: https://github.com/kafitzgerald/geocat-examples/actions/runs/7492945543

The 3.11 ubuntu-latest CI run used the retry step - others just ran through.