Revert "Propagate AlternateProtocolUsage enum from network service to browser"

This reverts commit edf429ba1a9b4c7db472a815ff5c49c41f720577.

Reason for revert: Many failures related to alternate_protocol_usage: https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20ChromiumOS%20MSan%20Tests/30706/overview

Example: 
Uninitialized value was stored to memory at
#0 0x560d7a2db8c9 in Serialize ./gen/services/network/public/mojom/alternate_protocol_usage.mojom-shared.h:95:13

Original change's description:
> Propagate AlternateProtocolUsage enum from network service to browser
> and blink service.
>
> In some cases, Chrome fails to use HTTP/3 even when the server
> supports HTTP/3, so it'll be useful to show the reason in the DevTools.
> The reason is to be expressed as AlternateProtocolUsage(enum), and
> the function to calculate it has already been implemented in network service.(https://crrev.com/c/3897695)
>
> However, currently it has only the enums to describe why an alternative job or a DNS HTTPS job is used, so we should make them richer.
> Especially we should prepare the enum to tell why HTTP/2 is used
> even when the server supports HTTP/3.
>
> But the purpose of this CL is not to enrich the enum but to implement the function needed to propagate the enum. Specifically, we have to propagate the enum from network service to browser service and blink service in order to show it in the DevTools. This CL is in charge of that.
>
> Design Docs is here:
> https://docs.google.com/document/d/1SfMy7MMTbSn2C1RkPxnlnQdj9AnZ5-fQdEl0XO1s2ZQ/edit?usp=sharing
>
> Bug: 1345536
> Change-Id: I776e422b3462a3eb8e5f94467b6caae08c8233e7
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3890050
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Commit-Queue: Yoichiro Hibara <hibarayoichiro@google.com>
> Reviewed-by: Matthew Denton <mpdenton@chromium.org>
> Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
> Reviewed-by: Clark DuVall <cduvall@chromium.org>
> Reviewed-by: Reilly Grant <reillyg@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1050104}

Bug: 1345536
Change-Id: I657ed355b94918852869b974c8ee56d363448396
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3913406
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Igor Ruvinov <igorruvinov@chromium.org>
Commit-Queue: Igor Ruvinov <igorruvinov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1050192}
16 files changed
tree: d29d8e813233987abcd3c65f55e74b7120ea8634
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.