fix: dev: Removed `VowsAssertionError` and `_AssertionNotFoundError`

Should not have been here after merging the changes from refactoring for preggy.  Well, they’re gone _now_...
dev: chg: @refactor @minor Removed async aliases in Vows class

These classes are never accessed through the Vows class…and they’re not intended for client code use.
chg: dev: @minor Added comment “dividers”
chg: dev: @minor Put reporting-related vows into `tests/reporting/`
Bugfix release 2.0.1
Merge branch 'refs/heads/develop/2.0'

* refs/heads/develop/2.0:
  Bugfix release 2.0.1
  chg: dev: @minor Put reporting-related vows into `tests/reporting/`
  chg: dev: @minor Added comment “dividers”
  dev: chg: @refactor @minor Removed async aliases in Vows class
  fix: dev: Removed `VowsAssertionError` and `_AssertionNotFoundError`
Squashed commit of the following:

commit 4c317603436a02f39e0cab522b528818196cf748
Author: Zearin <zearin@gonk.net>
Date:   Mon May 27 15:16:21 2013 -0400

    chg: dev: @minor Added comment “dividers” in `pyvows.runner`

commit 6bf834505e4749ef12a546ce2c7f987d7351fe4b
Author: Zearin <zearin@gonk.net>
Date:   Sun May 26 12:30:39 2013 -0400

    new: dev: @refactor Turned runner into a package to allow multiple implementations

    Right now, only the old runner (pyvows.runner.gevent) is the only one that works.

    However, it passes tests for me, and the ABC class for runners will (in the future) allow pyvows to use the best available means to run tests according to the users’ system.

commit 83d12bd7fb9dfd1f2a73be1b2bcfb2905d5ccad8
Author: Zearin <zearin@gonk.net>
Date:   Sun May 26 12:17:22 2013 -0400

    dev: refactor: Use `«suite»:«batches»` dict in `Vows.run()`

    Out of all possible algorithms for running tests, a mapping of files (test suites) to a set of batches (marked with `@Vows.batch) offers the greatest flexibility for any runner implementation.
Minor 2.0.2 release
Python 2.0.3
Safer coverage
Manifest
Fixing VowsAssertionError reference
Version bump to 2.0.4
Don't run following tests if setup or topic raise an error
Reporting of errors in setup, topic, teardown
Add new `capture_error` topic decorator which restores old behaviour

Previously, all errors from topic functions were captured and returned
as the topic. Using this decorator on topic functions keeps that
behaviour, otherwise errors in topic functions are reported as errors.
Update tests which relied on old topic error behaviour to use new decorator
Add more comments and tweaks for PR 102
Merge pull request #102 from rcl33/fix-topic-errors

Fix #102 : Failures in `topic` (or `setup`) no longer set the topic value to the error itself.  If this occurs, nested tests aren’t run.  To retain the old behavior, use `@Vows.capture_error` on your topic function.  Thanks to @rcl33 for the fix!