Implement Assert object constructor

This patch creates an instanced Assert object. The following characteristics:

- Exclusive to test blocks, `QUnit.assert` is now inexistent
- API `QUnit.push` is now `assert.custom`, it works on the test context.
- API `QUnit.pushFailure` is now `assert.failure`, it works on the test context.
- `assert.ok` is now equalized to other assertions and uses `Test.prototype.push` as well
- **We don't have test assertion leaks anymore (#583), although, we need to patch the reporter interface to run asynced**
 
Ref #583

@4852aa3 and @97c9a9c are here only for reference, they shouldn't be included in a merge.
Looking at the usage here and in the custom assertion below (and in the updated API docs), I wonder if we should alias `assert.test.push` to `assert.push`. That way we could document `assert.push` along with the other assertion. That would make more sense then documenting `test.push` where is not obvious at all what `test` refers to.