GitLab

Chrome running in mash cannot directly access the ash aura window hierarchy.
Instead it must pass an ash window container id when a new window is being
opened.

* Convert dialogs to use container id when no explicit parent is available
* Remove ash dependencies from NetworkConnectDelegateChromeos, including
GetNativeWindow()
* Add DEPS to restrict access to ash from chrome/browser/chromeos/net

Also do some cleanup:
* Add class comments for captive portal and HaTS dialogs, which I audited.
They do not need to be fixed for mash because they are always displayed in the
default container.
* Fix include-what-you-use.

BUG=657021
TEST=chrome browser_tests

Review-Url: https://codereview.chromium.org/2452283003
Cr-Commit-Position: refs/heads/master@{#428569}