[bitnami/*] Remove relative links to non-README sections, add verification for that and update TL;DR section (#20967)

* [bitnami/*] Remove relative links to non-README sections and add verification

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Update Elasticsearch solution title

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Update .github/workflows/markdown-linter.yml

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

* Move enterprise string to the tl;dr section

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Fix typo in some READMEs

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Replace placeholders in the TLDR section

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Fix typo in some READMEs

Signed-off-by: Jota Martos <jotamartos@vmware.com>

* Revert "Update Elasticsearch solution title"

This reverts commit 9f437f9.

---------

Signed-off-by: Jota Martos <jotamartos@vmware.com>
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

Author: jotamartos

.github/workflows/markdown-linter.yml

@@ -33,6 +33,13 @@ jobs:
           # Create an empty file, useful when the PR changes ignored files
           touch "${TEMP_OUTPUT}"
           exit_code=0
+          for f in ${md_files}; do
+            # Looking for links that do not start with https, # or img
+            if grep --quiet --perl-regexp '\]\((?!(https|#|img))[^\)]*' $f; then
+              echo "::error:: Please ensure all links in $f starts with https, # or img"
+              exit 1
+            fi
+          done
           markdownlint -o "${TEMP_OUTPUT}" ${md_files[@]} || exit_code=$?
           while read -r line; do
             # line format:
@@ -53,4 +60,4 @@ jobs:
           if [[ $exit_code -ne 0 ]]; then
             echo "::error:: Please review linter messages"
             exit "$exit_code"
-          fi
+          fi

bitnami/airflow/README.md

@@ -11,19 +11,17 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/airflow
+helm install my-release oci://registry-1.docker.io/bitnamicharts/airflow
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Apache Airflow in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
 This chart bootstraps an [Apache Airflow](https://github.com/bitnami/containers/tree/main/bitnami/airflow) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Apache Airflow in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -521,7 +519,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/airfl
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/airflow/values.yaml)
 
 ## Configuration and installation details