Using more objects in memory during checkout

I've been trying to address some points we always consider when thinking of how to resolve / improve spree performance. Working with objects in memory, doing less `object.reload` and saying good bye to famous `order.update!`.

I started by trying to reduce db queries / ar object loads when adding items to cart (`order.contents.add`), could go as far as running about half less db queries, see https://gist.github.com/huoxito/3d8bcf0d8fa24f54f429, and I've been trying to somehow benchmark this but I'm not really sure how to do it best yet.

These are some from a simple `Benchmark.measure` script https://gist.github.com/huoxito/2e0bc0b97420eb032329. The difference is not much at all really from a simple default spree install (with sample data only). But I'm curious to see how this would go with some more real world store scenario.

Also started looking at the transition from address => delivery and made some changes on the Stock::Estimator to reduce the number of hits on db as well.

I couldn't make all specs pass yet mostly because I'd need more time to catch where is it exactly we're missing fresh data and using the out of date objects from the database (there are some NOTEs on the code though that should help narrow down the hot spots). 

Overall I feel like the end result here is going to be more code and possibly more complex code but I can't really see how else we can achieve better performance. Personally every time I've done something like `order.reload` is because I had lost track of the method calls and just reloading the object, or everything inside spree, would be the easiest way to go.

will still try to make those specs green but I wanted to share this with everyone to get feedback since I've spent already quite a decent amount of time on it.

// @BDQ @JDutil 
it's pretty much the same reason here https://github.com/huoxito/spree/commit/dfdaa4610c84cca366a6547978f3c543a790b07b, we should always create the adjustment from the adjustable, e.g. `adjustable.adjustments.create`. This let us keep working with the same instances, no reloads, via the collection `adjustable.adjustments`. I hadn't realized this myself until recently:

```ruby
irb(main):001:0> post = Post.create
=> #<Post id: 5, title: nil, created_at: "2014-12-05 01:25:52", updated_at: "2014-12-05 01:25:52">
irb(main):002:0> post.comments
=> #<ActiveRecord::Associations::CollectionProxy []>
irb(main):003:0> Comment.create post: post
=> #<Comment id: 3, message: nil, post_id: 5, created_at: "2014-12-05 01:26:05", updated_at: "2014-12-05 01:26:05">
irb(main):004:0> post.comments
=> #<ActiveRecord::Associations::CollectionProxy []>
irb(main):005:0> post.reload.comments
=> #<ActiveRecord::Associations::CollectionProxy [#<Comment id: 3, message: nil, post_id: 5, created_at: "2014-12-05 01:26:05", updated_at: "2014-12-05 01:26:05">]>
```