Implement sanitize done page in SWA

Back to Safety (Sanitize) is a feature that aims to provide a soft reset
for the ChromeOS. In the initial versions, we would reset some ChromeOS
settings, some Chrome settings, and disable extensions. However, in the
future more "soft reset" features would be added to the project (such as
network settings reset). This project is behind a feature flag and was
previously using just a pop up dialog in the ChromeOS Settings. However,
it seems like this feature needs to have a standalone dialog for which
it is being migrated to SWA.
This CL only aims to create a static UI before more technical aspects of
the project are connected to it. Basically for now the Sanitize
process would be ChromeOS Settings -> Run Sanitize -> SWA Done dialog.
And this CL is only focusing on the latter part of this (only SWA).
Once the SWA is set up, the initial running of the feature will be moved
to the SWA as well, as opposed to the current dialog opening inside the
ChromeOS settings.

Screenshot1: https://screenshot.googleplex.com/tqTure8xGXpBNcd
Screenshot2: https://screenshot.googleplex.com/9Q44RyLv5XuEsrV

BUG=b:332697577, b:319446147, b:340724224

Change-Id: I4f58b414733f67d966363165f1bec129c7d8b163
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5581212
Commit-Queue: Behnood Momenzadeh <behnoodm@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: John Admanski <jadmanski@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1315859}
28 files changed
tree: 1fe1c431fa8373f07d6fe4a0ec1d12f6411d566c
  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.