Add a buildflag to use the handle verifier in a per module mode.

The HandleVerifier prevent you from using any ScopedHandle during a module initialization (i.e. if a DLL use one in DllMain this will call back into its host executable that hasn't been initialized yet and things will derail). In this CL I'm adding a build flag to make it possible to use it in a single module mode..

Committed: https://crrev.com/a89708a5c1bfe778ed1615f0bc92f0e9ae2e2192
Cr-Commit-Position: refs/heads/master@{#398361}

BUG=618205

Review-Url: https://codereview.chromium.org/1977833003
Cr-Original-Commit-Position: refs/heads/master@{#398575}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 82ef0204161f34381ab832a576c4789e1063e0ee

common.gypi

@@ -1631,6 +1631,13 @@
       }],
       ['OS=="win"', {
         'windows_driver_kit_path%': '$(WDK_DIR)',
+        'conditions': [
+          ['component!="shared_library"', {
+            'single_module_mode_handle_verifier%': 0,
+          }, {
+            'single_module_mode_handle_verifier%': 1,
+          }],
+        ],
       }],
       ['os_posix==1 and OS!="mac" and OS!="ios"', {
         'conditions': [