[rust] Fix local architecture discovery in Selenium Manager

[bonigarcia]

Description

This PR fixes a bug reported in #11517, related to the architecture discovery (e.g., arm64, x86_64) in Selenium Manager.

Motivation and Context

So far, the Selenium Manager logic relied on a Rust standard constant called std::env::consts::ARCH for the architecture discovery. According to its doc, this constant is "A string describing the architecture of the CPU that is currently in use". Nevertheless, when compiled for a x86_64, like in CI (for instance, for macOS, using cargo build --release --target x86_64-apple-darwin), that constant is always x86_64 (even when executed in a macOS M1). The solution I found to fix this issue is to rely on the command uname (in UNIX/Linux) and the environment variable (PROCESSOR_ARCHITECTURE) in Windows for the automatic discovery of the underlying architecture.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[diemol]

I see issue #11517 is closed, is this still needed?

[bonigarcia]

Yes, this PR still needs to be merged.

[diemol]

👍
Can you please fix the conflicts so we can merge?