Split our base Validator into an InputValidator and BusinessValidator.

Introduce an IAmValidatable interface to mark types that we want to be
able to implicitly validate.
Introduce DynamicCommandValidators for Input and Business.

Begin to amend CommandValidatorProvider to build these dynamic validators
when no explicit command validators are available
We might discover more than one validator for a type, so created a
composite validator to allow us to combine them... not sure this is a good
idea but we can see...
Changes to quick start sample to simulate dynamic command validators
Unsaved changes... d'oh!
Got the spike working! :-)

Had to use IValidator rather than IValidator<IAmValidatable> which means
using an obsolete method on FluentNHibernate.  Just going with that for
now...

We need to use the old CompositeValidator for all validators now (even
single ones) as it is responsible for converting the validator to
IValidator<IAmValidatable>.

Needs cleaned up and specs put around it.
Renamed ValidatorWrapper to ComposedValidator - better expresses what it is
Renamed "Dynamic" validators to "Composed" validators

Avoid any confusion about dynamics.  Better expresses concept.
Add specs for composed validators
Oh dear... fixed a horrible bug in ConceptAs..

Infinite recursion on equality check!  Dearie, dearie me..
Merge branch 'master' of https://github.com/dolittle/Bifrost.git into DynamicCommandValidatorsSpike
Forgot the changed files in the Silverlight project...