[🚀 Feature]: Selenium-Manager falls back to the latest driver version if a given version still needs to be released

[bonigarcia]

Feature and motivation

Continuation of #11334. When a given driver version is unavailable in its repository (e.g., chromedriver 110), Selenium Manager should fall back to the latest version.

Usage example

./selenium-manager --browser chrome --browser-version dev

... and dev exists on the machine, but the required driver version (e.g., chromedriver 110) has not been released yet.

[github-actions]

@bonigarcia, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[titusfortner]

Just to be clear.

Assume versions:
Production: v100
Beta: v101
Dev: v102
Canary: v102

When Dev exists on the machine, but chromedriver v102 hasn't been released yet through regular channel, then Selenium Manager should get v101.

[bonigarcia]

Completed with #11454.