Initialize configuration as early as possible

The first workaround I put in for the unexpected side-effects of PowerMock was sufficient to make my unit tests happy but failed to resolve the problem in real-world scenarios. This release moves the workaround to the earliest point I could find... the interception of the ParentRunner.run() method. This is well before the PowerMock runner gets started, which should avoid the configuration failure.