Fix Session failing run using the chromerdriver binary

[luigibarbato]

This PR addresses an issue where session execution is failing due to compatibility problems with the current ChromeDriverManager. At the moment, running the session has become increasingly complex and prone to errors.

To mitigate this issue temporarily, this fix introduces a direct approach: passing the ChromeDriver binary explicitly. This solution ensures stability and functionality until ChromeDriverManager is updated with the latest improvements and repositories.

Given the current limitations of the ChromeDriverManager, this approach provides a straightforward and effective workaround to unblock session execution while waiting for upstream fixes.

Changes

• Updated the session configuration to accept the ChromeDriver binary path directly.
• Temporarily bypassed the dependency on ChromeDriverManager until its updates resolve the underlying issues.

Next Steps

• Monitor updates to ChromeDriverManager for fixes or improvements.
• Once updated, evaluate the feasibility of reverting to the default management approach.

[xchwarze]

I understand that the correct thing would be something like this:

        driver_path = os.path.join(os.path.expanduser("~"), ".cache", "selenium", "chromedriver", "win64", "132.0.6834.110", "chrome.exe")
        chrome_path = os.path.join(os.path.expanduser("~"), ".cache", "selenium", "chrome", "win64", "132.0.6834.110", "chrome.exe")
        options.binary_location = chrome_path
        options.browser_executable_path = chrome_path
        options.driver_executable_path = driver_path

my example is from windows

[luigibarbato]

exactly

[xchwarze]

I don't think you understood what I'm saying that what you did is wrong... doing what you did could unconfigure undetect driver.
the correct thing to do is to fix the undetect driver configuration that way.