Dropping the view from Presenter#onDestroy was idiotic.

"Originally," onDestroy was setting view = null. This broke
the more recently introduced loaded flag. I fixed that by making
onDestroy call dropView() instead.

But I don't remember why onDestroy was clearing the view in the first
place. I suspect it was a bad fix for problems that have sinced been
better corrected by severing the connection between onResume and
onLoad, and by debouncing onLoad. Certainly when I drop this and
play with sample apps through rotation and sample death, nothing bad
is happening.

The onDestroy behavior was fundamentally wrong: it breaks the
ability for dropView to be called out of order, the whole reason
it requires a view argument in the first place. This is particularly
a problem when a presenter is declared in a higher scope than the
views it is running.
Merge pull request #67 from square/ray/dont-go-like-that

Dropping the view from Presenter#onDestroy was idiotic.
Update change log for 0.11
[maven-release-plugin] prepare release mortar-parent-0.11
[maven-release-plugin] prepare for next development iteration
Kill MortarContext in favor of getSystemService()

Warning: This is an API-breaking change.

Casting made it difficult to interoperate with other context wrappers,
since Mortar's would always need to be outermost.  We still keep the
name of the system service lookup private.

Activities have a little more work to do, but not much.  It may or may
not prove worthwhile to introduce helpers for that work later.
update docs for MortarContext removal
Merge pull request #70 from square/loganj/kill_mortarcontext

Kill MortarContext in favor of getSystemService()
Adding tests for PopupPresenter