Add new user-agent specific bfcache blocking reasons

As part of the project that enables bfcache on pages with the Cache-control: no-store header, Chromium will evict the bfcache-eligible page if it has ever used WebSocket, WebRTC, or WebTransport. Add new reason strings to reflect these cases.

See https://github.com/fergald/explainer-bfcache-ccns/blob/main/README.md for more background.

Author: lozy219

source

@@ -98825,6 +98825,14 @@ interface <dfn interface>NotRestoredReasons</dfn> {
    <code>RTCDataChannel</code> was shut down, so the page was not in a state that could be stored in
    the <a href="#note-bfcache">back/forward cache</a>. <ref>WEBRTC</ref></dd>
 
+   <dt>"<dfn data-x="blocking-rtc-used-with-ccns" export><code>rtc-used-with-cache-control-no-store</code></dfn>"</dt>
+   <dd>The <code>Document</code> was created from an HTTP response whose
+   `<code data-x="http-cache-control">Cache-Control</code>` header included the
+   "<code data-x="">no-store</code>" token, and it has created a <code>RTCPeerConnection</code> or
+   <code>RTCDataChannel</code> which might be used to receive sensitive information, so the page was
+   not in a state that could be stored in the <a href="#note-bfcache">back/forward cache</a>.
+   <ref>HTTP</ref> <ref>WEBRTC</ref></dd>
+
    <dt>"<dfn data-x="blocking-sensors" export><code>sensors</code></dfn>"</dt>
    <dd>The <code>Document</code> <span data-x="request-sensor-access">requested sensor
    access</span>.</dd>
@@ -98893,11 +98901,25 @@ interface <dfn interface>NotRestoredReasons</dfn> {
    <dd>The <code>Document</code> used the Web Share API's <code
    data-x="dom-Navigator-share">navigator.share()</code> method.</dd>
 
+   <dt>"<dfn data-x="blocking-websocket-used-with-ccns" export><code>websocket-used-with-cache-control-no-store</code></dfn>"</dt>
+   <dd>The <code>Document</code> was created from an HTTP response whose
+   `<code data-x="http-cache-control">Cache-Control</code>` header included the
+   "<code data-x="">no-store</code>" token, and it has created a <code>WebSocket</code> connection
+   which might be used to receive sensitive information, so the page was not in a state that could be
+   stored in the <a href="#note-bfcache">back/forward cache</a>. <ref>HTTP</ref> <ref>WEBSOCKETS</ref></dd>
+
    <dt>"<dfn data-x="blocking-webtransport" export><code>webtransport</code></dfn>"</dt>
    <dd>While <span data-x="unload a document">unloading</span>, an open <code>WebTransport</code>
    connection was shut down, so the page was not in a state that could be stored in the <a
    href="#note-bfcache">back/forward cache</a>. <ref>WEBTRANSPORT</ref></dd>
 
+   <dt>"<dfn data-x="blocking-webtransport-used-with-ccns" export><code>webtransport-used-with-cache-control-no-store</code></dfn>"</dt>
+   <dd>The <code>Document</code> was created from an HTTP response whose
+   `<code data-x="http-cache-control">Cache-Control</code>` header included the
+   "<code data-x="">no-store</code>" token, and it has created a <code>WebTransport</code> connection
+   which might be used to receive sensitive information, so the page was not in a state that could be
+   stored in the <a href="#note-bfcache">back/forward cache</a>. <ref>HTTP</ref> <ref>WEBTRANSPORT</ref></dd>
+
    <dt>"<dfn data-x="blocking-webxr" export><code>webxrdevice</code></dfn>"</dt>
    <dd>The <code>Document</code> created a <code>XRSystem</code>.</dd>
   </dl>