[BUGFIX beta] controllers have new QP values before setupController

New QP values weren't getting set until finalizeQueryParamChanges, but they
should have been set before `setupController` is called, and this change fixes
that.

I commented out a test case for an extremely unlikely corner case where the
active class will be incorrectly calculated if the user types in a
non-Ember-generated, unpruned URL, but I intend to fix this all in an active 
class refactor shortly, but it's better to get this fix in than delay.