New rule: Forbid QUnit 1.x syntax

[platinumazure]

Per the migration guide, this implies a few warnings (which may or may not be separate rules):

• Forbid use of module, test, and asyncTest globals
• Forbid use of QUnit.asyncTest
• Forbid global stop()/start()
• Require assert.async() instead of QUnit.stop()
• Forbid use of assertion globals
• Forbid use of global expect()
• Require beforeEach and afterEach module hooks instead of setup and teardown
• Forbid QUnit.push (use this.push in custom assertion)
• Forbid QUnit.init
• Forbid QUnit.reset
• Forbid assignments to QUnit.log and other logging callbacks
• Forbid QUnit.jsDump, favoring QUnit.dump instead

[platinumazure]

Unfortunately we don't have a way of intelligently distinguishing between QUnit.start() for starting the test runner and QUnit.start() for decrementing the async semaphore. We want to flag the latter but not the former.

Hopefully it should be sufficient to flag asyncTest/QUnit.stop and nudge users to use assert.async; the documentation for assert.async should in turn inform users on the correct way to use the new async callback mechanism.