[🚀 Feature]: Selenium-Manager fails when a browser version is specified

[bonigarcia]

Feature and motivation

Continuation of #11334. When a browser version is specified in Selenium Manager (using --browser-version), for instance, an unstable version (e.g., beta, dev, or canary/nightly), instead of falling back to the latest driver, Selenium Manager should raise an error.

Usage example

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

... and dev doesn't exist on the machine.

[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!

[bonigarcia]

Completed with #11399.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.