[dotnet] Use Selenium Manager to locate drivers on PATH

[titusfortner]

Dependencies

Don't evaluate this PR until the following have been merged:
* #12342
* #12343
* Also I think this breaks Appium so I need to redo it without changing all the method parameters.

Description

• Driver Finder is only used in Default service constructor
• Removed DriverFinder usage in Driver constructor; it only needs to happen when a default Service class is created because that is the only place a user does not have to specify it, and we do not want to remediate.
• No longer need special Safari Technology Preview handling in Service; SM handles it based on Options
• I made the driver url parameter optional because we no longer use it, and deleted those constants
• Allows user to pass full path to driver in the Service class constructor to match other bindings; should reduce the number of backwards compatibility issues (see [🐛 Bug]: Selenium Manager and.NET #12301)

Motivation and Context

• Implements [🚀 Feature]: Selenium Manager check drivers on PATH #11356 for .NET

Considerations

This is not backwards compatible from the standpoint that if a user started the service with a random path and it wasn't valid, the code would ignore it and look on PATH or use Selenium Manager. This was a bug (#12301)

[diemol]

Do we need to fix the Firefox tests before merging this? Seems Chrome usually passes after a retry.

[titusfortner]

The issue is on trunk as well. Somehow we're losing the geckodriver connection and I don't know why. It passes locally, and usually passes on retry.

[diemol]

Yes, I was running them locally and they all pass. Strange.