DrupalApplication should use the compiled container

Problem/Motivation

\Drupal\Core\Command\DrupalApplication::bootstrap() contains the following code:

      // We need to not load a cached copy of the container from disk. For
      // example, inside Kernel tests, we need to fully build the container so
      // we discover and register commands, instead of reusing the container
      // from the Kernel test itself. Therefore, we pass `FALSE` for the
      // `$allow_dumping` parameter here.
      $kernel = new DrupalKernel('prod', $this->classloader, FALSE);

Why should the command line use a ContainerBuilder container? This does not feel correct.

Proposed resolution

The reason why this was necessary for kernel testing is because of the changes made by \Drupal\KernelTests\KernelTestBase::register to the container.

Use the context to be able to set things about the kernel to make testing commands in KernelTestBase simple but still use a regular dumping kernel when not testing.

Remaining tasks

User interface changes

None

Introduced terminology

N/a

API changes

N/a

Data model changes

N/a

Release notes snippet

N/a