[🚀 Feature]: Make Selenium Manager classes thin wrappers

[titusfortner]

Status

• Java — [java] Selenium Manager generates output from argument list  #13385
• Ruby — [rb] update SOC for driver finder and selenium manager classes #13386
• .NET — [dotnet] Making SeleniumManager a thin wrapper #13833
• Python — [py] update SOC for driver finder and selenium manager classes #13387
• JS — [js] Making SeleniumManager a thin wrapper #13853

Feature and motivation

Make Selenium Manager class only responsible for locating the correct binary, and executing that binary with the provided arguments.

The DriverFinder class parses any options and service class details required and sends them to Selenium Manager.

This allows:

• better separation of concerns between DriverFinder and Selenium Manager (see [py] moved static method get_path to SeleniumManager class #12554)
• creating a Server class to get the grid with Selenium Manager (see [rb] implement downloading grid with Selenium Manager #12299)
• releasing SM as a separate package (would be an alternative to [🚀 Feature]: Release Selenium Manager binaries #11694, and would provide support for projects to use older versions of Selenium.

[diemol]

Do you mean having something like DriverService but for SM?

[titusfortner]

Yes, I guess it's essentially that.

[diemol]

Implemented in all bindings.

[github-actions]

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