Experiment with continue-on-error for flaky tests in GitHub actions

[shoyer]

• Closes #xxxx
• Tests added
• User visible changes (including notable bug fixes) are documented in whats-new.rst
• New functions/methods are listed in api.rst

[ianhi]

I think this might have some unintended consequences.

Just for this PR I'd suggest introducing a failure in the non-flaky pytest to make sure the job still fails. My memory of how this works is that if job will not turn red.

I see now. But beware that i think this means the flaky test will always be green now

[ianhi]

Is this a real command. I don't see it in here: https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax

[ianhi]

ahh wait I was confused by this being below. this impacts the continue-on-error above?

[dcherian]

I think the real oslution here may be to move the pydap backend out to pydap itself, as we have done with the rest.