Fix inaccuracies in stretch clusters documentation

- Remove incorrect organization=redpanda requirement from TLS prerequisites
  (the bootstrap command uses "Redpanda" as default, and this detail is
  unnecessary for users since the command handles it automatically)

- Update status command validation list to match actual implementation:
  pod health, TLS validity, Raft state, unique cluster names, peer
  consistency, and CA consistency

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

Author: JakeSCahill

modules/deploy/pages/redpanda/kubernetes/k-stretch-clusters.adoc

@@ -59,7 +59,7 @@ Before deploying a Stretch Cluster, ensure you have:
 
 * **TLS certificates for inter-operator communication**:
 ** ECDSA P-256 certificates (not RSA)
-** Shared Certificate Authority (CA) with `organization=redpanda`
+** Shared Certificate Authority (CA)
 ** Individual certificates for each operator signed by the CA
 ** Subject Alternative Names (SANs) including all service FQDNs and IP addresses
 ** Both ServerAuth and ClientAuth key usage
@@ -433,11 +433,12 @@ rpk k8s multicluster status \
 
 This command validates:
 
-* StretchCluster resource existence and status
-* NodePool binding and configuration
-* Cross-cluster secret synchronization
-* Broker health across all clusters
-* Spec consistency across clusters
+* Operator pod health and deployment configuration
+* TLS certificate validity and Subject Alternative Names (SANs)
+* Raft consensus state and leader agreement
+* Unique cluster names across all peers
+* Peer configuration consistency
+* CA certificate consistency across clusters
 
 === Operators not forming Raft cluster