This is to keep the sandbox as vanilla as possible, as it's the
environment that migrations should be built against.

Wrap the custom user classes in a conditional block.

This can be used by new Oscar installs.  It's the same as a the core
Django one but without a username.

The new model must have an email field but Oscar will work without
anything else.

These are simpler as they are guaranteed to have an email field which
Oscar uses for authentication.

* Emailbackend: Updated to use REQUIRED_FIELDS
* Demo and sandbox site now use compat.AUTH_USER_MODEL as well
* Added example custom user that gets tested for Django >= 1.5

It assumed there was a basket user.

This alters the benefit model to allow proxy class to be registered.
The dashboard flow is tweaked to allow such classes to be selected once
they've been registered.

A dummy custom benefit is included in the sandbox.

Remove customisation which now lives in the 'demo' site.

Example sites now sit in their own folder (sites) for easier
organisation.