chore(docs): cloud doc changes (automated) (#16050)

* chore(docs): automated cloud documentation update

* Enhance documentation for environment variables features

Clarified the search and filter functionality for environment variables and improved the explanation of system variables visibility in the backend tab.

---------

Co-authored-by: shahednasser <shahednasser@users.noreply.github.com>

Author: shahednasser

www/apps/cloud/app/environments/environment-variables/page.mdx

@@ -60,6 +60,29 @@ These variables are automatically set by Cloud and don't need to be configured m
 
 ---
 
+## Search and Filter Environment Variables
+
+You can search and filter the environment variables using the toolbar above the environment variables table:
+
+- **Search**: Enter a key name or value in the search field to filter the list in real time.
+- **Build / Runtime toggles**: Show only variables available at build time, only those available at runtime, or both at once.
+- **System Variables toggle**: Show or hide system-managed variables. System variables are hidden by default.
+
+---
+
+## System Environment Variables Visibility
+
+In addition to the [system environment variables](#system-environment-variables) documented above, the backend tab displays all system-provided variables alongside your user-defined ones when the **System Variables** toggle is enabled. These are variables that Medusa adds to your environment, such as database URL, Redis URL, and other relevant variables.
+
+System variables are visually distinguished from user-defined variables with a subtle background and muted text. Because Medusa manages those:
+
+- The edit and delete actions are not available for system variables.
+- Secret system variables do not show the reveal (eye) icon.
+
+System variables are useful to understand what variables Medusa sets for you so that you don't add them as well.
+
+---
+
 ## Add Environment Variables on Cloud
 
 To add environment variables to an environment:
@@ -179,4 +202,4 @@ A file download will start with the name `env.txt`, which contains the environme
 
 You can rename the file to `.env` and use it in your local development.
 
-![Export env button in the environment's settings tab](https://res.cloudinary.com/dza7lstvk/image/upload/v1767790560/Cloud/CleanShot_2026-01-07_at_14.55.48_2x_ro5bib.png)
+![Export env button in the environment's settings tab](https://res.cloudinary.com/dza7lstvk/image/upload/v1767790560/Cloud/CleanShot_2026-01-07_at_14.55.48_2x_ro5bib.png)

www/apps/cloud/generated/edit-dates.mjs

@@ -12,7 +12,7 @@ export const generatedEditDates = {
   "app/logs/page.mdx": "2026-05-06T11:31:50.584Z",
   "app/update-medusa/page.mdx": "2026-01-08T08:54:50.149Z",
   "app/connect-storefront/page.mdx": "2026-01-08T08:50:31.830Z",
-  "app/environments/environment-variables/page.mdx": "2026-06-09T12:12:26.314Z",
+  "app/environments/environment-variables/page.mdx": "2026-07-14T15:49:50.427Z",
   "app/environments/long-lived/page.mdx": "2026-06-18T13:40:26.814Z",
   "app/environments/preview/page.mdx": "2026-05-20T13:20:57.494Z",
   "app/faq/page.mdx": "2026-04-14T10:44:08.191Z",