Add workflow to build Selenium Manager in CI (for Windows, Linux, and macOS)

[bonigarcia]

Description

This PR creates a GH Actions workflow to build Selenium Manager for the three main operating systems: Windows, Linux, and macOS. This workflow is manually triggered. The objective is to use the generated binaries (attached as artifacts at the end of the workflow execution) in the future releases of Selenium Manager.

Motivation and Context

This PR is part of the development of Selenium Manager M1. Since it is non-trivial to cross-compile Rust (e.g., generate a Windows binary from a macOS machine), we can use the virtual environments of GH Actions (windows-latest, ubuntu-latest, and macos-latest) to that aim.

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.

[titusfortner]

The goal is to just generate the binaries? Where are they stored? I thought upload-artifact just allowed things to be used by other actions?

[bonigarcia]

Yes, the goal is just to generate the Selenium Manager binaries, for Windows, Linux, and macOS. The binaries can be downloaded from GH, in the workflow execution page. You can see an example here:

https://github.com/bonigarcia/rust-examples/actions/runs/3220624172

We can manually get these binaries and include then in the Selenium releases, if finally we decide to do it that way.

[titusfortner]

Though, downside is github doesn't support M1, yet.

[diemol]

Thank you, @bonigarcia!