Use nested Runner for QUnit test execution

QUnit extension now wraps the code execution and executes QUnit methods using JUnitCore.

However, JUnitCore creates a separate process, which:

1/ Prolongs the test execution
2/ Reduces information about current bootstrap path and classpath, leading to strange errors
3/ Creates another level of indirection, which is difficult to be debugged.