Because mock objects have their own imposterizer, they have everything
they need to imposterize themselves, except the invokable target and
ancilliary protocols.

The additional 'imposterize' method is a special case that moves the 
knowledge needed to imposterize the mock object (where itself is the
target) including the LRCaptureControl protocol into the mock, where
this knowledge belongs.
By having the expectation builder act as an invokable itself, it can
call the imposterizeTo: method on the mock imposter directly, shifting
the assumption that a mock is defined by conformance to the Imposterizable
protocol rather than the CaptureControl protocol.

There was some semantic value to the CaptureControl protocol but ultimately
it seemed like a layer of indirection too far.

The LRExpectationsTest is able to much more easily create an imposterized
mock object now without knowing the finer details of how it happens.
The mockery no longer needs an imposterizer - they are self-contained
within the LRMockObject class.

If we ever need to make the imposterizer implementation an extension point,
then we can add it back to the mockery and inject it into mocks as a
dependency, but until then this is nicer.
Provide a unified interface for mocking classes and protocols.

Give all mocks a default name.
Added an example that supports the WIP documentation.
Support returning values directly.
Started work on new README.
Updating the podspec.