Use Selenium 4 based docker containers in FallbackConfig

[jtnord]

The containers should match the selenium version. using old version 3 containers is not a good idea :)

this got missed in #973
@uhafner I think you are the only user of the container support.

based on #1043 and #1045 this probably needs some testing in the consumer.

https://hub.docker.com/r/selenium/standalone-firefox/tags?page=1&name=4.6.0
https://hub.docker.com/r/selenium/standalone-chrome/tags?page=1&name=4.6.0

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jtnord]

core.InstallWizardTest.wizardInstallCustomPluginsTest failed is so flaky of late :(

Also noting a conflict with #1073

[uhafner]

Are we creating incremental ATH versions? Then I can use the snapshot in my Selenium upgrade PR. Seems that Jenkins still is building this PR...

[jtnord]

Are we creating incremental ATH versions? Then I can use the snapshot in my Selenium upgrade PR. Seems that Jenkins still is building this PR...

I don't think we do.
in the interim you can try version 999999-20230323.135212-4 which I just deployed from this code.

[uhafner]

This breaks all of my tests:

https://github.com/jenkinsci/warnings-ng-plugin/actions/runs/4577019077/jobs/8081916367?pr=1470

[uhafner]

Another broken test:

https://github.com/jenkinsci/git-forensics-plugin/pull/577/checks?check_run_id=12404986224
or
https://ci.jenkins.io/job/Plugins/job/git-forensics-plugin/job/PR-577/1/testReport/io.jenkins.plugins.forensics.git/ForensicsPluginUiTest/docker_11___Build__docker_11____shouldAggregateToolsIntoSingleResult/