Change WebRTC IP handling policy from multiple booleans to an enum.

chrome/browser/extensions/api/preference/preference_api.cc

Index: chrome/browser/extensions/api/preference/preference_api.cc
diff --git a/chrome/browser/extensions/api/preference/preference_api.cc b/chrome/browser/extensions/api/preference/preference_api.cc
index fa7e8695e4bf8b44658f0d6a2f8fed6a5d86c365..283732b00cfa162fcf424c35d0c2085854cb5876 100644
--- a/chrome/browser/extensions/api/preference/preference_api.cc
+++ b/chrome/browser/extensions/api/preference/preference_api.cc
@@ -119,9 +119,7 @@ PrefMappingEntry kPrefMapping[] = {
     {"translationServiceEnabled", prefs::kEnableTranslate,
      APIPermission::kPrivacy, APIPermission::kPrivacy},
 #if defined(ENABLE_WEBRTC)
-    {"webRTCMultipleRoutesEnabled", prefs::kWebRTCMultipleRoutesEnabled,
-     APIPermission::kPrivacy, APIPermission::kPrivacy},
-    {"webRTCNonProxiedUdpEnabled", prefs::kWebRTCNonProxiedUdpEnabled,

[pthatcher1, 2015/10/21 00:06:53]

Is this going to break the existing Network Limiter extension?  How are we going
to transition the extension to the new API?  Can the extension do version
checks?

[juberti2, 2015/10/21 00:58:40]

Agree with this concern. I think we need to handle the case where the IP
handling policy is set, or, if not set, check for the old multiple routes
preference. Otherwise, users who set the pref manually and old extension users
will regress when the new version of Chrome rolls out.

+    {"webRTCIPHandlingPolicy", prefs::kWebRTCIPHandlingPolicy,
      APIPermission::kPrivacy, APIPermission::kPrivacy},
 #endif
     // accessibilityFeatures.animationPolicy is available for