chore: create Discover category with JTBD and CQA 2.1 compliance

Move architecture overview, server components (7 sub-pages), user
workspaces, and supported platforms from the Administration Guide
into a new top-level Discover module. This is the first step in the
JTBD category restructure — promoting evaluation and discovery
content out of the monolithic Administration Guide.

Changes:
- Create modules/discover/ with pages, examples, and images
- Add WHY-first abstracts to all 11 pages ("To [purpose], [action]")
- Add page-aliases for backward-compatible URLs from admin-guide
- Update antora.yml: register discover nav, move architecture
  diagram collector to discover module
- Update all cross-module xrefs in admin-guide, overview modules
- Remove Discover entries from administration-guide nav.adoc

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: gtrivedi88

antora.yml

@@ -7,6 +7,7 @@ start_page: overview:introduction-to-eclipse-che.adoc
 nav:
   - modules/overview/nav.adoc
   - modules/hosted-che/nav.adoc
+  - modules/discover/nav.adoc
   - modules/end-user-guide/nav.adoc
   - modules/administration-guide/nav.adoc
   - modules/extensions/nav.adoc
@@ -133,6 +134,6 @@ ext:
   - run:
       command: ./tools/create_architecture_diagrams.py
     scan:
-      base: modules/administration-guide/images/architecture/
+      base: modules/discover/images/architecture/
       dir: build/collector/architecture-diagrams
       files: '*.png'

modules/administration-guide/nav.adoc

@@ -2,18 +2,7 @@
 
 * xref:security-best-practices.adoc[]
 * xref:preparing-the-installation.adoc[]
-** xref:supported-platforms.adoc[]
 ** xref:installing-the-chectl-management-tool.adoc[]
-** xref:architecture-overview.adoc[]
-*** xref:server-components.adoc[]
-**** xref:che-operator.adoc[]
-**** xref:devworkspace-operator.adoc[]
-**** xref:gateway.adoc[]
-**** xref:dashboard.adoc[]
-**** xref:che-server.adoc[]
-**** xref:che-devfile-registry.adoc[]
-**** xref:plugin-registry.adoc[]
-*** xref:user-workspaces.adoc[]
 ** xref:calculating-che-resource-requirements.adoc[]
 * xref:running-at-scale.adoc[]
 // Install

modules/administration-guide/pages/architecture-overview.adoc

@@ -22,7 +22,7 @@ Persistent volume claims facts:
 
 * {prod-short} does not create persistent volumes in the infrastructure.
 * {prod-short} uses persistent volume claims (PVC) to mount persistent volumes.
-* The xref:devworkspace-operator.adoc[Dev Workspace operator] creates persistent volume claims.
+* The xref:discover:devworkspace-operator.adoc[Dev Workspace operator] creates persistent volume claims.
 +
 Define a storage class name in the {prod-short} configuration to use the storage classes feature in the {prod-short} PVC.
 

modules/administration-guide/pages/configuring-storage-classes.adoc

@@ -31,7 +31,7 @@ config:
       schedule: '0 */4 * * *' # cron expression with backup frequency
     imagePullPolicy: Always
 ----
-<1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:devworkspace-operator.adoc[{devworkspace} operator overview].
+<1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:discover:devworkspace-operator.adoc[{devworkspace} operator overview].
 <2> The `--insecure` flag can be required depending on the integrated registry's routing configuration.
 
 **Note:** The `path` field must contain the URL to your OpenShift integrated registry given by the cluster.

modules/administration-guide/pages/devworkspace-backup-integrated-openshift-registry.adoc

@@ -31,7 +31,7 @@ config:
       schedule: '0 */4 * * *'
     imagePullPolicy: Always
 ----
-<1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:devworkspace-operator.adoc[{devworkspace} operator overview].
+<1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:discover:devworkspace-operator.adoc[{devworkspace} operator overview].
 
 The `authSecret` must be named `devworkspace-backup-registry-auth`. It must reference a {kubernetes} Secret of type `kubernetes.io/dockerconfigjson` that contains credentials to access the registry.
 The secret should be created in the installation {namespace} for the {devworkspace} operator.

modules/administration-guide/pages/devworkspace-backup-regular-oci-registry.adoc

@@ -7,10 +7,10 @@
 [id="preparing-the-installation"]
 = Preparing the installation
 
-To prepare a {prod-short} installation, learn about the {prod-short} ecosystem and deployment constraints:
+To prepare a {prod-short} installation, review the platform requirements and deployment tools:
 
-* xref:supported-platforms.adoc[]
+* xref:discover:supported-platforms.adoc[]
+* xref:discover:architecture-overview.adoc[]
 * xref:installing-the-chectl-management-tool.adoc[]
-* xref:architecture-overview.adoc[]
 * xref:calculating-che-resource-requirements.adoc[]
 * xref:understanding-the-checluster-custom-resource.adoc[]

modules/administration-guide/pages/preparing-the-installation.adoc

@@ -18,5 +18,5 @@ spec:
                 value: $OPERATOR_INSTALL_NAMESPACE <1>
             name: che-dashboard
 ----
-<1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:devworkspace-operator.adoc[{devworkspace} operator overview].
+<1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:discover:devworkspace-operator.adoc[{devworkspace} operator overview].
 ====