support non default mobile web browsers for testing

[vdelendik]

We've found a problem with elements detection on non-default web browsers like: firefox, samsung native browser etc.
Need to play with appium capabilities to be able to recognize elements. As first variant we have to test approaches with automationName:

• Appium
• Selenoid

[vdelendik]

we are moving custom browsers arguments and options into the AbstractCapabilities.java.
It makes sense to test samsung browser options and incorporated if works into above class:
Samsung browser:

NB. when v8 stable is released you can use with 'com.sec.android.app.sbrowser'

options.add_experimental_option('androidPackage', 'com.sec.android.app.sbrowser.beta')
options.add_experimental_option('androidActivity', 'com.sec.android.app.sbrowser.SBrowserMainActivity')
options.add_experimental_option('androidDeviceSocket', 'Terrace_devtools_remote')
options.add_experimental_option('androidExecName', 'Terrace')

NB. chromedriver will need to be in your path! (Or change this to your specific path)

driver = webdriver.Chrome('chromedriver', chrome_options=options)

Details: https://medium.com/samsung-internet-dev/how-to-use-webdriver-and-chromedriver-to-automate-samsung-internet-e1249814823e

[vdelendik]

with new w3c compatible capabilities we have more chances to incorporate those feature. Ideally we have to provide just example of the valid capabilities to test it as no changes expected in 6.3.30+ on core code

[akamarouski]

Let's wait appium 2.0 in mcloud