Add `setupActivity` helper

This runs through the whole creation lifecycle for the Activity of the passed class and then returns it. Makes the simplest tests (where you just test interaction) less verbose. Might also make documentation and basic Robolectric examples a little less daunting.

I think one drawback might be that it hides the `ActivityController` which might be something we want to expose as much as possible :confused:.