[dotnet] Declare selenium manager binaries as content

[nvborisenko]

Description

It allows selenium manager to be included into installers, like msi/exe or vsto.

Motivation and Context

Fixes #12577

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.

[Sigrec]

Not sure if this is the best place to ask but, is there a nightly build for this?

[titusfortner]

No, but we'd like to. I think nuget supports them. @diemol did we look into this? Are we limited by bazel?

[diemol]

@nvborisenko said they need to be pushed with a beta suffix or something like that. I don't think bazel is blocking us. We are just very short on time.

[Sigrec]

Follow up to this fix, how can I change where the web driver looks for selenium-manager to the self-contained executable itself (ClickOnce), as it still checks the current working directory path where the .exe resides? Or maybe I'm just doing something wrong or missing something.

[nvborisenko]

Selenium manager should be inside of your ClickOnce app, and it should be unpacked when you deploy/install your app. Thus you don't care about selenium manager location, it should just work.

If it doesn't, please create new issue.

[Sigrec]

Issue created #12842 found out the issue is when publishing to a single file.