Stop running arc container on supervised user creation flow

chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc

Index: chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
diff --git a/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc b/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
index 08e387c875da8b092ca97b9006d2cb95acfe69c6..4a1ae7394db11cb358f4834c4123de659df918c0 100644
--- a/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
+++ b/chrome/browser/chromeos/login/supervised/supervised_user_login_flow.cc
@@ -46,6 +46,10 @@ bool SupervisedUserLoginFlow::CanLockScreen() {
   return true;
 }
 
+bool SupervisedUserLoginFlow::CanStartArc() {
+  return false;

[achuithb, 2016/11/30 19:03:12]

Is this correct?

[yoshiki, 2016/12/02 16:07:56]

We don't allow ARC for supervised user. 

Actually, it is also blocked in ArcSessionManager and we don't need to set
"false" here.
https://cs.chromium.org/chromium/src/chrome/browser/chromeos/arc/arc_session_...

[achuithb, 2016/12/02 20:38:55]

Interesting. I know there are some use cases where supervised users are used in
schools, etc (even though this is not what we recommend). Ok.

+}
+
 bool SupervisedUserLoginFlow::ShouldLaunchBrowser() {
   return data_loaded_;
 }