[IOSSignout] Clear Device Data on Signout for Managed Accounts

This device adds the new flow for managed users' signout. The new flow is as follows:

1. User signs out of a managed account
2. An alert is displayed informing the user that any data not saved to their account will be cleared.
3. If the user continues with sign-out, their device data from the time of sign-in is deleted. If the time was not known, then data for all time will be deleted. Note: the data types deleted are the data types that allow partial deletion, which have been added as a new constant in `browsing_data_remove_mask.mm`.
4. If the user chooses to cancel sign-out, then no changes will be made to their data and they will not be signed out.

The new logic for managed users is controlled by a feature flag and independent of the sync/signin features. The feature will first be enabled in the field trial test config before rollout.

Screenshot: https://drive.google.com/file/d/1uUmCyoEFgSaN4UHEzPU2FsqwUgmhdXX1/view?usp=drive_link
Recording: https://drive.google.com/file/d/1p1ISw6A3H3hTTszb6dTnN45_EXywl_yT/view?usp=drive_link

Low-Coverage-Reason: OTHER the low coverage is for the fake delegate and features files
Bug: 340599928
Change-Id: If5bdf7d977944fac10d6f952d6975f5765650883
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5527342
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Commit-Queue: Salma Elmahallawy <esalma@google.com>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1305894}
17 files changed
tree: 729be4426e376148f961df357c6bbd070425e08d
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.