fix button_exact, text_exact for uiautomator2 driver

[rajdeepv]

currently, text_exact method throws Selenium::WebDriver::Error::NoSuchElementError if used with appium-uiautomator2-server. This is because findByUiAutomator uses only the first selector (Which we send as description and not text)

public UiSelector findByUiAutomator(String expression) throws UiSelectorSyntaxException {
        List<UiSelector> parsedSelectors = null;
        UiAutomatorParser uiAutomatorParser = new UiAutomatorParser();
        final List<UiSelector> selectors = new ArrayList<UiSelector>();
        try {
            parsedSelectors = uiAutomatorParser.parse(expression);
        } catch (final UiSelectorSyntaxException e) {
            throw new UiSelectorSyntaxException(
                    "Could not parse UiSelector argument: " + e.getMessage());
        }

        for (final UiSelector selector : parsedSelectors) {
            selectors.add(selector);
        }
        return selectors.get(0);
    }

[jsf-clabot]

All committers have signed the CLA.

[KazuCocoa]

Thanks!
ruby_lib has similar methods in other places. So, we should fix them as same.

Could you try #544 branch?
I use XPath strategy instead of uiautomator to fix this issue. So, your tests may work with #544, I think.

[rajdeepv]

XPath strategy also works

[KazuCocoa]

Thanks! @rajdeepv

I'll check #544 more with other OS versions and release ruby_lib as 9.4.0 soon.
So, I close this PR.

[rajdeepv]

Thanks @KazuCocoa

[KazuCocoa]

Just published as v9.4.0 @rajdeepv