Added the acceptance and specs folder for the scenarios.
Tomorrow I'll continue working on the scenarios for behat by completing
the EndToEndScenario test and using it to create the FeatureContext in acceptance.

PS: I noticed that amaka ; runs the default task without whining for the missing
task name. Is this a bug or a feature, if so it should be documented. Good candidate
for the first acceptance test.
Ensured that Behat runs w/o errors
WIP: completing the Behat infrastructure
Completed code for autoloading sub-contexts
Renamed EndToEndScenario to EndToEndSpecContext and added superclass SpecContext
Working on acceptance tests, running specs from global behat fails due to autoload.
Renamed error-handling-and-reporting to script-loading
Completed the specification for amaka script loading
Fixed the wrong-task-running-default bug.
Updated copyright in files header
Added PHP Mess Detector as dev dependency (required by :build). Updated dependencies
Minor renaming
Specified the new Amaka error reporting and resolution system
Wired up the amaka error R&R system to the rest of the program
(relates to previous commit) Renamed Trigger::errorFromException to Trigger::fromException
Refactored the Error Resolution subsystem and introduced the Resolution class.
Refactored ErrorReporting\Trigger and added a ref. to the previous exception to errors and failures. Improved the error messages
Completed the basic introduction of ScriptScope and DispatchTable,
which now simply forwards calls to 'task' to the old 'task' method
on the AmakaScript.
The Scope refactoring is almost complete.
Beginning to work on cleaning up