Right now, MaterialDesignController::Initialize() is getting cluttered with initialization of unrelated items. It's there because those things need to also be initialized along with the MaterialDesignController.

MaterialDesignController::Initialize() is called from many locations throughout the code-base for various tests that don't start up a full browser. Rather than pepper all those same locations with these changes, they're placed here to minimize code changes and to ensure no places are missed. Ideally, there would be a more general, "initialize random stuff here" function into which these things can be placed, including the call to MaterialDesignController::Initialize().