Description

• each of the bindings look for SE_MANAGER_PATH environment variable for Selenium Manager first before looking in the standard location

Motivation and Context

• Allows users to override the bundled copy of Selenium Manager which could be useful for:
  • debugging with unreleased binary
  • using custom build on non-supported architecture
  • designating the location from a package manager (e.g., Conda)
  • putting in a directory with known permissions
• This is an alternate solution to [🚀 Feature]: Cache Selenium Manager #11359
  • Java is the only language that uses SM in a temp directory for each process and would benefit from a standard location; no good reason to move the binary for other languages
  • Using an environment variable is a more flexible solution for package managers (see conversation in fix for conda install of selenium-manager #12536)
  • The cached directory would change per Selenium release, where SM in a directory with environment variable won't need to be moved when Selenium is updated (useful for custom builds and package managers)
  • This code is much more straightforward and easier to maintain than [rb] copy selenium manager binary to cache and use from there #12547 & [java] Copy SM binary to cache folder and use it from there (#11359) #12539