[feature] BrowserSteps element finder could use type=password or type=email etc if the input element is unique

Often for browsersteps it will come up with some complicated path which could change, like `//foo/div/span/p/input` for selecting the login/password input field

but better would be to check `type` if its unique and use that?

```
//input[@type='password']
```

same as `button`

this might make the locator more resilient

Start by locating the BrowserSteps element-finder entry point and trace how it currently builds paths for input and button elements. Verify the behavior with unique password or email inputs, such as //input[@type='password'], and confirm that the existing path remains the fallback when the type is not unique.

Written by the indexing model from the issue text.