Subliminal does not expose UIAElement.setValue despite -[SLKeyboard typeString:] warning

[aaronpang]

EDIT: Rewritten to make the below less Inkling-specific and to reference existing bugs. -- @wearhere

UIAutomation can't type "tap-hold" characters such as "’" (curly quote) (#91).
When asked to type such characters, Subliminal detects UIAutomation's failure and falls back upon setting text fields/views' values directly (#95). Because this behavior may be confusing from the standpoint of a user watching the tests, or the application observing changes to the text, Subliminal logs a warning when it does so.

This warning may be undesirable for several reasons:

• it makes the logs noisier;
• when Subliminal logs a warning, UIAutomation automatically takes a screenshot whose name is the warning message. But because the warning in this case will contain a special character, certain environments e.g. Jenkins may consider the screenshot to have an invalid filename, causing errors down the line.

So, it would be nice if Subliminal exposed UIAElement.setValue so that developers could call that in contexts where they knew that -[SLKeyboard typeString:] would end up logging the warning.