Jumbo: Fix a build error in components/content_settings

The build error occurs if using `use_jumbo_build=true` in GN
configuration. The same variable name is used in the anonymous namespace
of content_settings_registry.cc and website_settings_registry.cc. It can
cause a name conflict during merging both files.

TBR=raymes@chromium.org
NOTRY=true

Bug: none
Change-Id: I33eeb5ff00a2ab113d28a63f0044442375b98df2
Reviewed-on: https://chromium-review.googlesource.com/1212422
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Reviewed-by: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#589400}

components/content_settings/core/browser/content_settings_registry.cc

@@ -21,8 +21,8 @@ namespace content_settings {
 
 namespace {
 
-base::LazyInstance<ContentSettingsRegistry>::DestructorAtExit g_instance =
-    LAZY_INSTANCE_INITIALIZER;
+base::LazyInstance<ContentSettingsRegistry>::DestructorAtExit
+    g_content_settings_registry_instance = LAZY_INSTANCE_INITIALIZER;
 
 // TODO(raymes): These overloaded functions make the registration code clearer.
 // When initializer lists are available they won't be needed. The initializer
@@ -73,7 +73,7 @@ std::set<ContentSetting> ValidSettings(ContentSetting setting1,
 
 // static
 ContentSettingsRegistry* ContentSettingsRegistry::GetInstance() {
-  return g_instance.Pointer();
+  return g_content_settings_registry_instance.Pointer();
 }
 
 ContentSettingsRegistry::ContentSettingsRegistry()

components/content_settings/core/browser/website_settings_registry.cc

@@ -15,7 +15,7 @@
 namespace {
 
 base::LazyInstance<content_settings::WebsiteSettingsRegistry>::DestructorAtExit
-    g_instance = LAZY_INSTANCE_INITIALIZER;
+    g_website_settings_registry_instance = LAZY_INSTANCE_INITIALIZER;
 
 }  // namespace
 
@@ -23,7 +23,7 @@ namespace content_settings {
 
 // static
 WebsiteSettingsRegistry* WebsiteSettingsRegistry::GetInstance() {
-  return g_instance.Pointer();
+  return g_website_settings_registry_instance.Pointer();
 }
 
 WebsiteSettingsRegistry::WebsiteSettingsRegistry() {