Extract containers

Well, containers and objects, really. Haven't addressed metadata at all yet. That'll come next once these idioms are solid.

Still a little unclear how I want to represent objects that are created as a result of an API call (and, thus, definitely proxy for resources in the Rackspace cloud) and objects created via the SDK (but are not necessarily representative of objects in the cloud), e.g.,

```ruby
# This is a Container containing data on a server-side container
container = cf.containers.all.first

# versus this Container which is a client-side created container
container2 = cf.containers["foo"]
```

I'm pretty sure I want one consistent idiom for unsynch'd objects (still trying to find a good term for that) vs synch'd ones.
> But it's a little closer to ActiveRecord.

Hmm? [`#all`](http://api.rubyonrails.org/classes/ActiveRecord/Scoping/Named/ClassMethods.html#method-i-all) doen't take arguments, does it? You can use it in a chain with `.where` methods and such, but then it reads as "all instances where such-and-such is foo".

> `list` feels a little Java-like as a name goes.

Ouch! :sob: The wounds!

Counterpoint: our [API docs](http://docs.rackspace.com/files/api/v1/cf-devguide/content/GET_listcontainers_v1__account__accountServicesOperations_d1e000.html) call it "list containers".