[HEAD BROKEN] DrupalUnitTestBase and this container and transliteration and kernel and whatnot

The - private $baseContainer; is just cruft I nuked.

Then I would need to reopen the bootstrap kernel patch which I won't.

Edit: the patch name comes from not having an issue id so I just thrown in some random garbage. Whatever to get the issue done at 5am.

To clarify, tests use $this->container which is set by TestBase to drupal_container() which worked fine until some test like the transliteration test decided to pull something out of CoreBundle -- and as $this->container was not reassigned after Kernel init, that service is not there. The transliteration test is not guilty. I think I am.

WebTestBase calls TestBase::rebuildContainer which does

    $this->kernel = new DrupalKernel('testing', FALSE, drupal_classloader(), FALSE);
    $this->kernel->boot();
    $this->container = drupal_container();

so those tests contain an up to date container. Now DrupalUnitTestBase does too by storing the container as it is being built. You know, PHP objects, they are passed around by handler so as the build finishes it's the exact same object in drupal_container and this->container.