docs: renamed getting-started.sh -> getting_started.sh (#390)

# Description

*Please add a description here. This will become the commit message of the merge request later.*

Author: Felix Hennig

docs/modules/trino/examples/getting_started/code/getting-started.sh renamed to docs/modules/trino/examples/getting_started/code/getting_started.sh

@@ -17,14 +17,14 @@ and apply it:
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=install-trino]
+include::example$getting_started/code/getting_started.sh[tag=install-trino]
 ----
 
 Wait for the Trino cluster to get ready:
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=watch-trino-rollout]
+include::example$getting_started/code/getting_started.sh[tag=watch-trino-rollout]
 ----
 
 == Verify that it works
@@ -49,7 +49,7 @@ Create a port-forward for the coordinator to access Trino easily in the next ste
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=port-forwarding]
+include::example$getting_started/code/getting_started.sh[tag=port-forwarding]
 ----
 
 === Access the Trino cluster via CLI tool
@@ -58,21 +58,21 @@ We use the https://trino.io/download.html[Trino CLI tool] to access the Trino cl
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=download-trino-cli]
+include::example$getting_started/code/getting_started.sh[tag=download-trino-cli]
 ----
 
 We need to make the CLI tool executable:
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=chmod-trino-cli]
+include::example$getting_started/code/getting_started.sh[tag=chmod-trino-cli]
 ----
 
 Now, run some queries against the coordinator. Show available catalogs:
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=retrieve-trino-catalogs]
+include::example$getting_started/code/getting_started.sh[tag=retrieve-trino-catalogs]
 ----
 
 which should output:
@@ -86,7 +86,7 @@ Check how many workers are connected to the coordinator:
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=retrieve-trino-workers]
+include::example$getting_started/code/getting_started.sh[tag=retrieve-trino-workers]
 ----
 
 which should output:
@@ -118,7 +118,7 @@ In order to remove the previously downloaded CLI tool, you can safely remove it
 
 [source]
 ----
-include::example$getting_started/code/getting-started.sh[tag=cleanup-trino-cli]
+include::example$getting_started/code/getting_started.sh[tag=cleanup-trino-cli]
 ----
 
 == What's next

docs/modules/trino/examples/getting_started/code/getting-started.sh.j2 renamed to docs/modules/trino/examples/getting_started/code/getting_started.sh.j2

@@ -18,7 +18,7 @@ After you have installed stackablectl, run the following command to install all
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=stackablectl-install-operators]
+include::example$getting_started/code/getting_started.sh[tag=stackablectl-install-operators]
 ----
 
 The tool will show
@@ -36,14 +36,14 @@ You can also use Helm to install the operators. Add the Stackable Helm repositor
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=helm-add-repo]
+include::example$getting_started/code/getting_started.sh[tag=helm-add-repo]
 ----
 
 Then install the Stackable Operators:
 
 [source,bash]
 ----
-include::example$getting_started/code/getting-started.sh[tag=helm-install-operators]
+include::example$getting_started/code/getting_started.sh[tag=helm-install-operators]
 ----
 
 Helm will deploy the operators in a Kubernetes Deployment and apply the CRDs for the Trino service (as well as the CRDs for the required operators). You are now ready to deploy Trino in Kubernetes.