Improved Support for Recorded Selectors

When using our Set of Mark (node id) implementation, we compute our own selectors to interact with the UI. Right now they are basic and don't create a fully unambiguous selector. We should expand our support/tests with cases where there is the same text in multiple places on the screen, etc.

Ideally we can use other elements like Parent View IDs, etc.