Create Mojo Struct for user information used in login/lock screen.

ash/public/interfaces/login_user_info.mojom

+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+module ash.mojom;
+
+import "ash/public/interfaces/user_info.mojom";
+import "mojo/common/string16.mojom";
+
+// Supported authentication types. Keep in sync with enum in
+// screenlock_bridge.h
+enum AuthType {
+  OFFLINE_PASSWORD,
+  ONLINE_SIGN_IN,
+  NUMERIC_PIN,
+  USER_CLICK,
+  EXPAND_THEN_USER_CLICK,
+  FORCE_OFFLINE_PASSWORD,
+};
+
+// Information about the custom icon in the user pod.
+struct UserPodCustomIconOptions {
+  string id;
+  mojo.common.mojom.String16 tooltip;
+  bool autoshow_tooltip;
+  mojo.common.mojom.String16 aria_label;
+  bool hardlock_on_click;
+  bool is_trial_run;
+};
+
+// Info about a user in login/lock screen.
+struct LoginUserInfo {
+  // User's basic information including account id, email, avatar etc.
+  UserInfo basic_user_info;
+
+  // True if this user is a desktop user.

[jdufault, 2017/06/14 02:20:42]

What is a desktop user? My best guess is that we're running in a
Windows/macOS/Linux build? In which case I think we should eliminate the
variable.

[xiaoyinh(OOO Sep 11-29), 2017/06/15 18:39:37]

Removed, thanks!

+  bool is_desktop_user;
+
+  // Supported authentication type for this user.

[jdufault, 2017/06/14 02:20:42]

What about

  // What method the user can use to sign in.

[xiaoyinh(OOO Sep 11-29), 2017/06/15 18:39:37]

Changed. Thanks!

+  AuthType auth_type;
+
+  // True if this user has already signed in.
+  bool is_signed_in;
+
+  // True if this user is the device owner.
+  bool is_owner;

[jdufault, 2017/06/14 02:20:42]

is_owner => is_device_owner

[xiaoyinh(OOO Sep 11-29), 2017/06/15 18:39:37]

Done.

+
+  // True if fingerprint unlock is allowed for this user.
+  bool allow_fingerprint_unlock;
+
+  // True if multi-profiles sign in is allowed for this user.
+  bool is_multiprofile_allowed;
+
+  // Enforced policy for multi-profiles sign in.
+  string multiprofile_policy;

[jdufault, 2017/06/14 02:20:42]

Do we know what values this can be? Can it be an enum instead of a string?

[xiaoyinh(OOO Sep 11-29), 2017/06/15 18:39:37]

The values seem to be harded coded here:
https://cs.chromium.org/chromium/src/chrome/browser/chromeos/login/users/mult...
Change it to an enum should be easy, I can do it in another CL if this is
desired. What do you think?

[jdufault, 2017/06/15 19:00:02]

Yes, an enum is much better. Can you refactor that code and land it as a CL
before landing this one? Then the first check-in is using the right approach.

+
+  // True if this user can be removed.
+  bool can_remove;
+};