feat: Link the CRD reference on the Stackable Hub

The docs' own pages now link https://hub.stackable.tech/crds instead of
the old CRD browser on crds.stackable.tech, using the new attributes:

  crd-ref: the listing
  {crd-ref}/<group>/<apiVersion>/<kind>{crd-ref-release}: a deep link

crd-ref-release is ?release=dev on this branch and gets the release
number on release branches (like crd-docs-version today).

The old crd-docs attributes stay until the operator repos migrate their
deep links to crd-ref (they do so in the planned operator sweep, one PR
per repo). page-crd-docs is removed: nothing in the UI templates reads
it.

The OIDC provider deep link loses its per-property anchor: the Hub has
section-level anchors only, so it points at #provider now.

Author: lfrancke

antora.yml

@@ -27,10 +27,14 @@ asciidoc:
     # Whether this version is already end of life.
     # If true, a banner will be displayed informing the user.
     end-of-life: false
-    # use the attributes below to link to the CRD docs
+    # The CRD reference on the Stackable Hub. crd-ref links the listing;
+    # deep links follow {crd-ref}/<group>/<apiVersion>/<kind>{crd-ref-release}
+    crd-ref: "https://hub.stackable.tech/crds"
+    crd-ref-release: "?release=dev"
+    # DEPRECATED: the old CRD browser attributes below are still used by the
+    # operator docs; they migrate to crd-ref repo by repo (operator sweep).
     crd-docs-base-url: "https://crds.stackable.tech"
     crd-docs: "{crd-docs-base-url}/{crd-docs-version}"
     # to make attributes accessible to the UI template, they need to
     # be prefixed with "page-"
-    page-crd-docs: "{crd-docs}"
     page-end-of-life: "{end-of-life}"

modules/ROOT/pages/index.adoc

@@ -118,7 +118,7 @@ xref:operators:index.adoc[Operator overview]
 
 Read the CustomResourceDefinition (CRD) reference for all CRDs that are deployed by any Stackable operator.
 
-{crd-docs}[CRD Reference {external-link-icon}^]
+{crd-ref}{crd-ref-release}[CRD Reference {external-link-icon}^]
 
 ++++
 </div>

modules/concepts/pages/authentication.adoc

@@ -38,7 +38,7 @@ In a diagram it would look like this:
 
 image::image$authentication-overview.drawio.svg[]
 
-NOTE: Learn more in the xref:tutorials:authentication_with_openldap.adoc[OpenLDAP tutorial] and get a full overview of all the properties in the {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/#spec-provider-ldap[AuthenticationClass LDAP provider CRD reference{external-link-icon}^].
+NOTE: Learn more in the xref:tutorials:authentication_with_openldap.adoc[OpenLDAP tutorial] and get a full overview of all the properties in the {crd-ref}/authentication.stackable.tech/v1alpha1/authenticationclass{crd-ref-release}#provider.ldap[AuthenticationClass LDAP provider CRD reference{external-link-icon}^].
 
 [#OIDC]
 === OpenID Connect
@@ -59,7 +59,7 @@ include::example$authenticationclass-keycloak.yaml[]
 <7> Optionally enable TLS and configure verification. When present, connections to the idP will use `https://` instead of `http://`. See xref:tls-server-verification.adoc[].
 <8> Trust certificates signed by commonly trusted Certificate Authorities.
 
-NOTE: Get a full overview of all the properties in the {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/#spec-provider-oidc[AuthenticationClass OIDC provider CRD reference{external-link-icon}^].
+NOTE: Get a full overview of all the properties in the {crd-ref}/authentication.stackable.tech/v1alpha1/authenticationclass{crd-ref-release}#provider.oidc[AuthenticationClass OIDC provider CRD reference{external-link-icon}^].
 
 [#tls]
 === TLS
@@ -113,4 +113,4 @@ include::example$authenticationclass-static-secret.yaml[]
 == Further reading
 
 * xref:tutorials:authentication_with_openldap.adoc[] tutorial
-* {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/[AuthenticationClass CRD reference{external-link-icon}^]
+* {crd-ref}/authentication.stackable.tech/v1alpha1/authenticationclass{crd-ref-release}[AuthenticationClass CRD reference{external-link-icon}^]

modules/concepts/pages/s3.adoc

@@ -284,4 +284,4 @@ region:
 
 == What's next
 
-Read the {crd-docs}/s3.stackable.tech/s3bucket/v1alpha1/[S3Bucket CRD reference{external-link-icon}^] and the {crd-docs}/s3.stackable.tech/s3connection/v1alpha1/[S3Connection CRD reference{external-link-icon}^].
+Read the {crd-ref}/s3.stackable.tech/v1alpha1/s3bucket{crd-ref-release}[S3Bucket CRD reference{external-link-icon}^] and the {crd-ref}/s3.stackable.tech/v1alpha1/s3connection{crd-ref-release}[S3Connection CRD reference{external-link-icon}^].

modules/reference/nav.adoc

@@ -1,4 +1,4 @@
 * Reference
-** {crd-docs}[CRD Reference {external-link-icon}^]
+** {crd-ref}{crd-ref-release}[CRD Reference {external-link-icon}^]
 ** xref:glossary.adoc[]
 ** xref:duration.adoc[]

modules/tutorials/pages/authentication_with_openldap.adoc

@@ -367,7 +367,7 @@ The LDAP connection details only need to be written down once, in the Authentica
 == Further Reading
 
 - xref:concepts:authentication.adoc[Authentication concepts page]
-* {crd-docs}/authentication.stackable.tech/authenticationclass/v1alpha1/[AuthenticationClass CRD reference{external-link-icon}^]
+* {crd-ref}/authentication.stackable.tech/v1alpha1/authenticationclass{crd-ref-release}[AuthenticationClass CRD reference{external-link-icon}^]
 - xref:superset:getting_started/index.adoc[Getting started with the Stackable Operator for Apache Superset]
 - xref:trino:getting_started/index.adoc[Getting started with the Stackable Operator for Trino]
 // TODO Operator docs for LDAP