Alphabetize the Dev Scope ordering

Relying on the default ordering doesn't seem to jazz w/ Java 8.
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.
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
DemoActivity can log scope hierarchy

Adding a menu option to DemoActivity to be able to log the scope hierarchy and easily inspect it.
Adding tests for PopupPresenter
Use getSystemService() to get the activity scope

Building on top of #70, which brought the great idea of using system services.

* Overriding `setContentView()` and manually inflating was not a good idea. It broke ActionBarSherlock support. It also created a useless extra context wrapper, for the sole purpose of providing the activity scope.
* Instead we let the activity provide the scope as a system service. Same goes for the application. More decoupling ensues.
* I also cleaned a few places in the doc that were leftovers from the `MortarContext` times.
Snip naive RxJava brain damage in DemoApplication
Bump to Java 1.7 and Android 19