[22.05] Bump version of chromedriver setup action

[mvdbeek]

Saw a failure on #15933, not sure if related.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[mvdbeek]

Seems that google would prefer that one uses https://googlechromelabs.github.io/chrome-for-testing/, but that's not been updated in the action ... and also it seems to work again now.

[mvdbeek]

I've also externalized the chromedriver setup into a reusable workflow. When nanasess/setup-chromedriver#191 gets merged we only need to update the action version in a single place, and we also don't need to run the setup in each job. We should probably do more of this, things like the client build in selenium could also just happen once.