Add WebSocket connection shutdown closure support

Summary:
This CL enhances the `EmbeddedTestServer` and `WebSocketConnection`
classes by adding support for registering shutdown closures.
This ensures WebSocket connections are safely disconnected when the
server shuts down. Additionally, APIs are updated to use pointer
arguments for consistency and ease of passing objects.

Details:
1. `EmbeddedTestServer` Enhancements:
   - Added `RegisterShutdownClosure` method to allow registering
     closures that are invoked before server shutdown completes.
   - `ShutdownOnIOThread` now calls all registered shutdown closures to
     ensure proper cleanup of WebSocket connections.

2. `WebSocketConnection` Enhancements:
   - Introduced a `shutdown_subscription_` member to manage the shutdown
     closure registration.
   - The constructor now accepts an `EmbeddedTestServer*` and registers
     a shutdown closure using `RegisterShutdownClosure`.

3. API Updates:
   - Changed `EmbeddedTestServer` arguments in relevant methods to
     pointers for consistency.
   - Updated `CreateWebSocketHandler`,
     `InstallDefaultWebSocketHandlers`, and related methods to use
     pointers instead of references.

4. Test Changes:
   - Adjusted tests and utility functions to pass `EmbeddedTestServer*`
     instead of references.

Reason for Change:
- To ensure safe cleanup of WebSocket connections during server
  shutdown, reducing the risk of dangling connections or resource leaks.
- Using pointer arguments simplifies API usage and aligns with Chromium
  coding conventions.

Bug: 40812029
Change-Id: I40b002435458b07e3415c8e2be70c4f55798bd37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6023255
Auto-Submit: Ryosuke Miyake <rysk@google.com>
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Huanpo Lin <robertlin@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1385450}
10 files changed
tree: f1c346c2d9f7afae565a4509cc1327762230cdf9
  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.