Update network request guide to include info about disabling logging (#5124)

* update command log guide to inform users they can disable logging

* add missing curly brace

* Update docs/guides/guides/network-requests.mdx

Co-authored-by: Matt Schile <mschile@cypress.io>

* add link to example of turning off all intercept logs

* lint fixes

* Update docs/guides/guides/network-requests.mdx

Co-authored-by: Bill Glesias <bglesias@gmail.com>

---------

Co-authored-by: Matt Schile <mschile@cypress.io>
Co-authored-by: Bill Glesias <bglesias@gmail.com>

Author: 3 people

docs/guides/guides/network-requests.mdx

@@ -525,8 +525,9 @@ cy.wait('@new-user').then(console.log)
 
 ## Command Log
 
-Cypress logs all `XMLHttpRequest`s and `fetch`es made by the application under
-test in the Command Log. Here is an example of what this looks like:
+By default, Cypress logs all `XMLHttpRequest`s and `fetch`es made by the
+application under test in the Command Log. Here is an example of what this looks
+like:
 
 <!-- Code to reproduce screenshot:
     cy.visit('https://jsonplaceholder.cypress.io')
@@ -541,6 +542,21 @@ test in the Command Log. Here is an example of what this looks like:
   alt="Screenshot of fetch and XHR requests"
 />
 
+:::info
+
+**Note:** Logging can be disabled by passing `{ log: false }` with the static
+response.
+
+```js
+cy.intercept('/users*', { body: ['user1', 'user2'], log: false }).as('getUsers')
+```
+
+To disable logs for all xhr/fetch requests, checkout our
+[example](/api/commands/intercept#Disabling-logs-for-a-request) on the intercept
+api page.
+
+:::
+
 The circular indicator on the left side indicates if the request went to the
 destination server or not. If the circle is solid, the request went to the
 destination server; if it is outlined, the response was stubbed by