[🚀 Feature]: Change version format in Selenium Manager

[bonigarcia]

Description

Currently, the versions of Selenium Manager are linked to the Selenium (bindings) releases. For example:

• Selenium 4.31.0 uses Selenium Manager 0.4.31
• Selenium 4.32.0 uses Selenium Manager 0.4.32
• Etc.

I propose to rethink this approach for several reasons. First, Selenium Manager is almost feature-complete. This way, we are starting to see empty releases of Selenium Manager, and this probably will happen in the future:

https://github.com/SeleniumHQ/selenium/blob/trunk/rust/CHANGELOG.md

Second, the sign-in process for Windows binaries will probably include a manual process. So, we would like to avoid releasing empty releases of Selenium Manager, unless necessary.

So, I propose to start Selenium Manager using its own version schema. We can start with version 1.0.0-beta1 (instead of 0.4.x). To implement this change, we need to consider the following changes:

• In Rust, the Selenium Manager version (sent to Plausible) is calculated using its own version (i.e., SM 0.4.32 corresponds to Selenium 4.32.0). Instead of this, a new flag should be required, for example, --selenium-version).
• The bindings should use this new flag to specify the Selenium version. I believe the Selenium version is specified with Bazel and shared among the different bindings.

Have you considered any alternatives or workarounds?

No response

[selenium-ci]

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

Selenium Triage Team: remember to follow the Triage Guide