Add Parent elements for Chrome spying mode

[LubosG]

This would make the web element identification for Chrome more precise, as we could define what element we actually want to work with, as most web pages do not really have unique values for all elements we would like to work with.
This way the nesting could be defined, which would definitely give us much higher chance to create a unique combination for more robust application model.

[LubosG]

I have recently found out, that there is a possibility to use chrome XPath inside the "Web Path" attribute in Application Modeller. That gives the ability to use a Parent XPath while specifying other attributes for the actual element. Using this technique I was able to successfully identify elements that previously were problematic. XPath example: "//*[@id="loginName"]"
Works perfectly with chrome dev tools XPath.