Request Class Issue #65

See also Pull requests #119

I've made the request class a first class object rather than use the static/facade interface used previously
That only really made sense if we had some DI container to manage it. Although given the use of some 'global' classes
in the code, the use of a DI container is looking more necessary. Something for the future.
I've also added codeception to composer and committed some basic start up stuff for that.
I think codeception looks better in terms of writing acceptance tests, over a selenium/sourcelabs framework.
doing some minor reformatting while we touch these files
pr #65 - Request Class - Inject Aura Web Request in constructor to aid unit testing.
pr #65 - Request Class - simplify parameter names
pr #65 - Request Class - Tidy up some namespacing and remove some use of globals
pr #65 - Request Class - Better autoloading using classInstantiate
pr #65 - Request Class - some docbloc fixes
pr #65 - Request Class - update tests
pr #65 - Request Class - all method

I decided against either having the request class either implement IteratorAggregate itself or make the parameterBag an object in it's own right,
and implemeting an iterator in that class, and just return the parameterBag as an array object. ArrayObject implements IteratorAgrregate anyway.
pr #65 - Request Class - Docbloc updates
Merge branch 'v160' into request-class1

Conflicts:
	admin/includes/classes/actions/class.zcActionAdminBase.php
Merge pull request #142 from zcwilt/request-class

Request class (Admin)