Page factory should not be global for processor resolver

[mikey]

Currently the page factory is global for all processors of a processor resolver. There needs to be a way to set the page factory depending on the processor, as some processors do not need a page factory or other require different page factories.

[mikey]

Doing this refactoring would result in a change of how the processor handles pages with the page factory, and enable refactoring of the memphis and xml processor in a way, that the cachable processor is a decorator which in turn can handle both as decorated instances.

[mikey]

First steps done with r1438, r1439, r1440 and r1441. Next step is to replace the stubAbstractPageProcessor with an interface, which is possible as all features from this class where moved to other places where they are better placed.

[mikey]

With r1442 processors must not longer take a page factory instance even if they are not page-based. Now the processor resolvers can be changed to enable per-processor page factories in environments with several different processors enabled. This will give a performance boost for non-page-based processors as well as there is no need to create a page factory for them any more.

[mikey]

Final steps done with r1445 and r1447. Now it is possible to set different page factories for different processors. Additionally now page factory code is loaded and executed if the selected processor does not require a page factory.