Moving ManagedNetworkConfigurationHandler to chromeos/.

Moving ManagedNetworkConfigurationHandler to chromeos/.

Also moving the dependencies of the handler to chromeos/:

NetworkUIData
from chrome/browser/chromeos/cros/network_ui_data*
to chromeos/network/network_ui_data*

NetworkPropertyUIData
from chrome/browser/chromeos/cros/network_ui_data*
to chrome/browser/chromeos/cros/network_property_ui_data*

CreateNetworkUIData
from chrome/browser/chromeos/net/onc_utils*
to chromeos/network/network_ui_data*

CertificatePattern
from chrome/browser/chromeos/cros/certificate_pattern*
to chromeos/network/certificate_pattern*

Certificate pattern matching (was a member function of CertificatePatern)
from chrome/browser/chromeos/cros/certificate_pattern*
to chrome/browser/chromeos/cros/certificate_pattern_matcher*

The only implementation change is in network_ui_data.cc in order to break dependency on EnumMapper.

NetworkUIData and CertificatePattern are data keeping classes only, and will eventually be replaced by ONC. However, we need them for backwards compatibility for a while.

BUG=180711
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=193364

[pneubeck (no reviews), 2013-04-08 08:22:06]

Hi Greg and Steven, you might like this one.

@Greg, please review. Thanks!
@Steven, I'll need your owner lgtm.

[gauravsh, 2013-04-08 16:56:20]

On 2013/04/08 08:22:06, pneubeck wrote:
> Hi Greg and Steven, you might like this one.
> 
> @Greg, please review. Thanks!
> @Steven, I'll need your owner lgtm.

Re: BUG=, perhaps this:
https://code.google.com/p/chromium/issues/detail?id=180711 ?

[Greg Spencer (Chromium), 2013-04-08 18:05:09]

LGTM.  Thanks for cleaning this up!

[stevenjb, 2013-04-08 19:22:33]

Nice cleanup. LGTM.

https://codereview.chromium.org/13454006/diff/11001/chromeos/network/network_...
File chromeos/network/network_ui_data.cc (right):

https://codereview.chromium.org/13454006/diff/11001/chromeos/network/network_...
chromeos/network/network_ui_data.cc:86: !certificate_pattern_.Empty()));
Is this logically not possible, or just unexpected? If unexpected it should
LOG(ERROR) instead of DCHECK. If not logically possible then this is fine.

[pneubeck (no reviews), 2013-04-10 08:59:22]

@Jochen, please lgtm the change to chrome/chrome_browser_chromeos.gypi

Thanks.

https://codereview.chromium.org/13454006/diff/11001/chromeos/network/network_...
File chromeos/network/network_ui_data.cc (right):

https://codereview.chromium.org/13454006/diff/11001/chromeos/network/network_...
chromeos/network/network_ui_data.cc:86: !certificate_pattern_.Empty()));
On 2013/04/08 19:22:33, stevenjb (chromium) wrote:
> Is this logically not possible, or just unexpected? If unexpected it should
> LOG(ERROR) instead of DCHECK. If not logically possible then this is fine.

Cleaned up. We better assume here that the input is not validated.

[jochen (gone - plz use gerrit), 2013-04-10 09:11:28]

lgtm

[commit-bot: I haz the power, 2013-04-10 09:12:01]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pneubeck@chromium.org/13454006/28001

[commit-bot: I haz the power, 2013-04-10 11:08:19]

Change committed as 193364