Allow \Drupal::setContainer when inspecting static calls to \Drupal

[mglaman]

Unit tests will mock the service container and often call \Drupal::setContainer. The GlobalDrupalDependencyInjectionRule rule should ignore calls to \Drupal when the method is setContainer or unsetContainer

[MPParsley]

Hi @mglaman, the Drupal docs often mention examples that are using static Drupal:: calls to get services but I wonder if it's a good practice to directly access the container as such?

[mglaman]

@MPParsley \Drupal::service is way easier for docs. But it can actually be a performance hit when not using proper dependency inject.

[mglaman]

Also, we should allow \Drupal:: anything in tests or Traits.