robot: separate robot tests and test_* pages

[haysmark]

The present doh.robot requires modifying your application code if you want to do any kind of acceptance/usability testing, where it really shines.

In DOH, you could test markup pages without modifying them by loading them in an iframe and pointing dojo.doc to the iframe's body. For the doh.robot, this is particularly valuable because it enables people to test their application code without modifying it, just like Selenium and Windmill. We should separate our test markup from the robot commands to demonstrate how this works, but it will require new APIs.

[haysmark]

Fixes #7521. Added new dojo.robotx and dijit.robotx APIs for writing robot tests outside of the markup they test. Separated existing robot tests from their markup. mouseMove arguments moved to match mouseMoveAt.

[Douglas Hays]

(In [14953]) References #7521. Reorder mouseMove parameters for API consistency.

[Douglas Hays]

(In [14954]) References #7521. Proxy commit for haysmark. Create robotx.js so that the robot can be separated from the unit test files Reorder mouseMoveAt parameters for API consistency. Drop new test_dnd unit test.

[Douglas Hays]

(In [14955]) References #7521. Proxy commit for haysmark. Create robotx.js so that the robot can be separated from the unit test files Drop new unit tests for form widgets.

[Douglas Hays]

(In [14956]) Fixes #7521. Proxy commit for haysmark. Reorder mouseMoveAt and nouseMove parameters for API consistency.