[🚀 Feature] [dotnet]: Release a separate Selenium Manager package with binaries

### Feature and motivation

Continuation of https://github.com/SeleniumHQ/selenium/issues/11694

We already have `Selenium.WebDriver` nuget package including selenium-manager binaries. What if selenium-manager binaries will be shipped as separate package?.. Let's say `Selenium.WebDriver.Manager`.

Why:
- Users will be able referencing to binaries if they want to deal with SM only (including SM process wrapper for .Net)
- `Selenium.WebDriver` will be depend on `Selenium.WebDriver.Manager`
- We will be able to release hotfixes of selenium-manager without releasing `Selenium.WebDriver` - user will be able to upgrade if he wants
- Disk/Network space optimization. If new version of main `Selenium.WebDriver` is released, user downloads <1MB data (instead of 10MB)

### Usage example

No specific usage, just restructuring packages and dependencies.

We also can consider creation of `Selenium Manager Tool`.
```bash
dotnet tool install -g SeleniumManager
seleniummanager --browser chrome --version 120
```

Command name is a topic for discussion.