[M137] Force the network speech synthesis extension to have a new extension id

Original change's description:
> Force the network speech synthesis extension to have a new extension id
> 
> Unfortunately, due to the enclosed bug, state about service workers seem
> to be cached in CHrome profiles. This appears to include code.
> 
> The end result is that any changes made to files e.g. audio.js, don't
> get loaded when the extension loads until the cache is deleted.
> 
> In order to work around the issue, update the network speech synthesis
> extension's key to force a new extension id. This appears to skip the
> cache at least for the first run to ensure the user gets the updated
> files.
> 
> This is not a long term solution and the enclosed bug still needs urgent
> attention from the extensions team.
> 
> R=akihiroota@chromium.org
> 
> Bug: 425464855
> Test: run with a new user profile p1. Make a breaking change to the extension. Verify extension is broken (no speech). Undo the breakage. Run with p1 again. Verify continued breakage. Update the extension manifest key. Run with p1 again. Verify speech works.
> Change-Id: I8f09cd5beab2361949c671f3c6bf21d57667f3e5
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6653391
> Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
> Commit-Queue: David Tseng <dtseng@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1475657}

Bug: 425929507,425464855
Change-Id: I8f09cd5beab2361949c671f3c6bf21d57667f3e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6655300
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/7151@{#2549}
Cr-Branched-From: 8e0d32ed6e49a2415b16e5ed402957cac2349ce2-refs/heads/main@{#1453031}
1 file changed
tree: b195fc5207e4255cd5fcef52429f61b2e9b5bfc0
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.