Added repository for handlers where an executable type can be mapped to a handler type
Created reflection method for finding all handlers in the application and finding the respective executable it handles
Created a method for setting up the repositories with information about the current application
Created all the basic steps needed to execute a command and query

There is no validation yet, and no handling of exceptions
All the default stuff should be in the default static class
The default parameter should be built into each step
Qvc should not fail when the handler throws an exception

Todo: add logging of exceptions, and add option to hide the exception in production environments
Handle the scenario where a command or query does not exist by forwarding the exception past all the other steps to the serializer step at the end.
Introduced interfaces for each step and a noop implementation for each step that only forwards the exception from the previous step to the next step.
If a handler does not exist then the rest of the pipeline should be skipped and the exception should be returned in the result object
When there are duplicate handlers the rest of the pipeline should be skipped and the exception should be returned in the result object
If making the handler fails with an exception then the rest of the pipeline should be skipped and the exception shoudl be returned in the result object