Adding :original to spree_api_key_layout override

Resolves warning:

    Deface: [WARNING][0m No :original defined for 'api_key_spree_layout', you should change its definition to include:
     :original => 'eb4b04993e8e4d1c20a7c3d974dfed20b59aec4c'

Fixes #3710
Remove blank username line in dummy database.yml mysql config

For some reason activerecord-jdbcmysql-adapter hates blank usernames
and will not connect despite the fact that mysql2 works fine. Removing
these lines doesn't break mysql2 so I see no reason to keep them there.
I'm trying to test my gems on jruby in anticipation of spree working on
jruby so this fix would be helpful. Here's sample Travis output showing
what goes wrong:
https://travis-ci.org/swrobel/spree_zero_stock_products/jobs/11136157

Fixes #3693
Finishing update begun in https://github.com/spree/spree/issues/3671

The change in https://github.com/spree/spree/issues/3671 helps ensure that spree 1.3.3 gets installed, but it appears that when multiple versions are installed, the `spree` command defaults to the most recent version. This way we'll make sure it's the 1.3.3 spree that's running the initialization for the new rails app.

Fixes #3724
Do not generate a new identifier for a payment when it is re-saved

Fixes #3733
Fix path to cart.png

Fixes #3747
asset-url needs TWO arguments in this branch
Fix product paging issue

Fixes #2851
Fixes #3064
Destroy order if import via api raises any error

So that no unintentionally partial order remains in the database

Fixes #3789
[api] Fix postgresql-specific error in Variants tests

The problem was we were passing a number to PostgreSQL for a string field (the permalink field). PostgreSQL spat the dummy because it doesn't know how to translate between strings and integers.
Remove defunkt orders/new.html.erb

Fixes #3799
Reversing order in which adjustments and line_items are destroyed when cart is emptied

See, e.g., https://github.com/spree/spree/issues/3787#issuecomment-25417823

Occasionally deleting the line_items before the adjustment will cause strange things to happen, like trying to recalculate the shipping and getting `nil` shipping amounts for shipments of no line items. Deleting the adjustments first and the line_items second seems a little cleaner in this way.

Also, philosophically it seems to make sense to empty a cart in the reverse order of how it was populated. So the cart begins with line items, to which handling and tax and shipping are added... Seems reasonable to "roll back" to a fresh cart by reversing the order and taking away the adjustments then the line_items.

If for some reason, the state gets stuck mid-emptying-of-cart, then you might be left with a user who's got their items but no shipping or tax charges. I'm not clear on whether `empty!` also rolls back the order state machine (which would prevent that bug), but I'm also not sure how concerned we should be about this possibility -- as opposed to the known issues that can sometimes happen when you delete the line_items first, rather than second.

I can see an argument both ways, but my opinion would be that this proposed order makes the most sense overall.

Fixes #3800
demonstrate bug in Spree::Product#save_master

Fixes #3746
fix bug in Spree::Product#save_master

Fixes #3746
Fix issue where sample variants were being created without stock levels
Include jquery.validate localization messages when the locale is not :en

Fixes #3794
Add a test for #3494
Fixed broken formatting of out-of-stock message for cart view.
Put improperly placed <br /> tag out of <span>.

Fixes #3826
Add validation for #3494
Create a custom router mapper so we have more control over the routes

Due to reasons explained in rails/rails#12367

Fixes problems like spree/spree#3757
Revert "Create a custom router mapper so we have more control over the routes"

This reverts commit b8d7e9ba27ae00aa3bdd49289bcddd6a2bb355b1.