Identify what must be done to be able to dogfood QA Tools

[rjkip]

It doesn't feel right that we will be offering QA Tools to the public yet don't use it ourselves. Identify the current QA configuration of QA Tools, what should be managed by QA Tools and what not (eg. Makefile), and what the most effective path is to dogfooding.

[rjkip]

In its current (3.0.0-alpha2) state, to be able to dogfood QA Tools, we would need to (not should):

1. Support individually configured rules, like increasing the minimum coupling-between-objects before the rule is triggered
   — I'd say too specific a feature. We can use the less optimal @SuppressWarnings annotations.

2. Allow registration of Mockery's TestListener
   — Mockery is switching to manual Mockery::close() calls.

3. Support for multiple test suites (unit:tests/unit, integration:tests/integration)
   — Feasible, I'd say. Also provide individual Ant targets to call from our Makefile or add QA Tools' Ant build file to .gitignore. Support multiple PHPUnit test suites #118

4. Support a PHPUnit bootstrap file (create or take existing). Support configuration of PHPUnit bootstrap file #119