No longer need to check for CheckoutController + OrdersController

They are always present because spree_frontend is a dependency of this gem

Fixes #61
Fixed two deface warnings for the admin side

Fixes #63
Fix on_hand behavior to be compatible with changes in Spree master

Fixes #64
Dont automatically assign admin role.

Please assign admin role manually now:

user = User.find(...)
user.spree_roles << Spree::Role.find_by_name("admin")

Fixes #66
Use correct calculator within checkout_spec (shipping, rather than generic)
It's not necessary to create a variant for checkout_spec tests
Add User#admin? method.

Fixes #67
Fix require for BarAbility in Admin::UsersController spec
Correct shipping method used in promotion adjustment spec
Manually assign admin role within promotion_adjustment_spec tests

This is due to f5c812a09661925afe8f22cf81d3d17ad5836764
No need for test for Admin::OrdersController#show permissions any more

This was removed as part of the shipments changes on spree/spree master
spanish locale added

Fixes #58
added error messages to reset password page
Bump selenium-webdriver to 2.32.0
Remove SslRequirement in favour of force_ssl

Fixes #45
Update original for user admin tab and hide the tab for users without authorization

Fixes #70
Add :original to admin_tab override

Related to #70
Change Devise Mapping to be spree_user, rather than just 'user'

This stop spree_auth_devise from clashing with any other Devise-backed User-model using configuration from applications.

While this *may* break existing applications, the change is necessary in order to prevent mysterious behaviour.

The mysterious behaviour I have seen today was that an application was using
Devise for its own User model, and the application was also using
spree_auth_devise which provides the Spree::User model, but defines a Devise
mapping of :user.

Due to spree_auth_devise overriding the Devise mapping for :user, the wrong user
class was being referenced in an omniauth callback, leading to undefined method
errors.

Moving spree_auth_devise over to a 'namespaced' mapping is the only way to
ensure that strange behaviour like this doesn't happen and that
spree_auth_devise is completely separate from any other authentication setup
within the main application.
Only depend on core, frontend, backend + API components
Set default host option for AM in password_reset_spec