`ShenandoahInitLogger` conditions its output on being in the generational mode. We can avoid this check by introducing a subclass of `ShenandoahHeap` and a new virtual method. This is really a "gateway" change for more substantive refactoring to better isolate the generational mode changes.