Bind the platform's lifecyle to the game controller
Add a default application adaptor
Synchronize robovm API updates
Merge branch 'expose_view_controller' of https://github.com/tomfisher/playn
Revert "Synchronize robovm API updates"

This is not in the beta-01 release and we're not using nightly snapshots right
now.

This reverts commit 2a6a2883b8a38ccdadc77b0edde0d7d162d5db30.
Some tweaks to new RoboVM lifecycle &c.

Everything still now revolves around the (soon to be renamed)
RoboRootViewController, but we keep a RoboPlatform.register() method just for
symmetry with the other platforms and because "simple" clients don't need to
know about RoboRootViewController.

This exposes a bit more in the archetype stub (creating a window and showing
it), but that's something you have to do on iOS always, so it's not going to
change, and it's useful to understand what the basic bootstrap stuff looks like
on iOS so that you have a starting point if you want to dig deeper.
RoboRootViewController -> RoboViewController.

It doesn't have to be a root view controller, it's just that in the normal
"PlayN is the whole app" use case.
Took care of an FPS TODO.