test: Add tests for W3C Actions

List of changes

Added Tests for W3C Actions, afterward we can remove the entire deprecated touch classes.

@laolubenson, Maybe the test class name can be improved, WDYT? another point to consider is how we are going to handle the ambiguous issue users will probably face.

using static OpenQA.Selenium.Interactions.PointerInputDevice;
using PointerInputDevice = OpenQA.Selenium.Appium.Interactions.PointerInputDevice;

Types of changes

What types of changes are you proposing/introducing to the .NET client? Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] New feature (non-breaking change which adds value to the project)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)

Documentation

[ ] Have you proposed a file change/ PR with appium to update documentation?
This can be done by navigating to the documentation section on http://appium.io selecting the appropriate command/endpoint and clicking the 'Edit this doc' link to update the C# example

Integration tests

[x] Have you provided integration tests to pass against the beta version of appium? (for Bugfix or New feature)

Details

Please provide more details about changes if it is necessary. If there are new features you can provide code samples showing how they work and possible use cases. Also, you can create gists with pasted C# code samples or put them here using markdown. About markdown please read Mastering markdown and Writing on GitHub

appium / dotnet-client