[Extensions] Handle extension acknowledgment of MV2 disabled stage

Chrome has announced that MV2 extensions will gradually no longer be
supported in the browser. None of these changes will take effect on any
Chrome channel before June, 2024. See more information at
https://developer.chrome.com/blog/resuming-the-transition-to-mv3.

The second stage of the deprecation will disable unsupported MV2 extensions and has user-visible notices in chrome://extensions.

This CL connects the 'keep for now' button in the extension's action
menu to acknowledge the notice for the rest of the stage. This means
when the button is clicked:
  - extension is removed from mv2 deprecation panel in
    chrome://extensions
  - mv2 deprecation message in chrome://extensions detail page is
    hidden for the rest of the stage.

For this we:
  - Notify ManifestV2ExperimentManager to update the "extension
    acknowledged in disabled stage" via
    developerPrivate.updateExtensionConfiguration
  - Listen for "extension acknowledged in disabled stage" pref changes
    via extension info updates

Screencast: https://drive.google.com/file/d/1aE0DL8oDD7rDYTdMsjuFFC5FWwWh4PMc/view?usp=drive_link
First, we open a browser in exp stage 1 (warning) and dismiss the
notice. Then, we open a browser in exp stage 2 (disabled), which has
the notice again, and dismiss the notice.

Bug: 339061151
Change-Id: I3ac8a5e7372a650d8972d39ae68f68cfc0df233f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5666466
Auto-Submit: Emilia Paz <emiliapaz@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1324668}
14 files changed
tree: 246da5b6d29ad6c41229edd4506b797a0e7f6838
  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.