Update UI references from Terraform to OpenTofu in documentation

Co-authored-by: JohannesRudolph <[email protected]>

Author: Copilot

docs/administration.building-blocks.md

@@ -76,15 +76,15 @@ in the future and even let you develop your own implementation types for Buildin
   to your customers. It can also be an easy option to evaluate if a need for a new building block definition exists.
   You just create a manual block and observe how many application teams use the definition.
   You can switch the definition to an automated building block in the future.
-- Terraform: this is the option to automate your Building Block. You only need a Terraform module and meshStack will
+- OpenTofu: this is the option to automate your Building Block. You only need an OpenTofu module and meshStack will
   run this configuration everytime a user adds a new Building Block to a meshTenant.
   In a later step you can setup Inputs for your
-  Terraform script. There is also a [section](#developing--deploying-a-terraform-building-block)
+  OpenTofu script. There is also a [section](#developing--deploying-a-terraform-building-block)
   below with further tips for developing Terraform Building Blocks.
 
-If you pick Terraform you have to enter a few further values:
+If you pick OpenTofu you have to enter a few further values:
 
-- Terraform Version: the version your Terraform modules shall be executed with.
+- OpenTofu Version: the version your OpenTofu modules shall be executed with.
 - Git Repository URL: the URL of the Git repository where your Terraform module resides.
 - (Optional) Git Repository Path: the specific directory in the repository where your Terraform module resides.
 - (Optional) Private SSH Key: This is needed and the only option to access private repositories.

docs/meshstack.building-aws-quickstart-guide.md

@@ -61,13 +61,13 @@ Before starting, ensure you have the following:
    - Notification user: receive notifications when things require their attention. This is set to your user by default.
    - Support & documentation: you can enter URLs that will be visible to users in the marketplace to request support or read more documentation.
 
-6. **Entering Terraform implementation details**
+6. **Entering OpenTofu implementation details**
 
-   If still on the general page, click “Next” and let’s start filling in all details for running Terraform as part of this building block.
+   If still on the general page, click “Next” and let’s start filling in all details for running OpenTofu as part of this building block.
 
    You will be asked which implementation type to use. Pick “Terraform” here. Additional settings will show up.
 
-   - Enter a desired Terraform version or leave the default value.
+   - Enter a desired OpenTofu version or leave the default value.
 
    > 💡Any versions entered over 1.5.5 will run using [OpenTofu](https://opentofu.org/).  
    > This is an open-source, friendlier alternative of Terraform.
@@ -100,7 +100,7 @@ Before starting, ensure you have the following:
 
    Click “Next” again, and you should see a modal pop-up with imported inputs, authentication, and outputs.
 
-   meshStack read out the Terraform files and automatically generated fitting inputs based on the defined variables, outputs, and providers.
+   meshStack read out the OpenTofu files and automatically generated fitting inputs based on the defined variables, outputs, and providers.
 
    Leave all of them checked and click “Add selected”.
 

docs/meshstack.how-to.create-your-own-platform.md

@@ -51,7 +51,7 @@ is not usable yet. Let's continue...
    - Supported Platform: select the platform type you created in Step 1.3
    - How often assigned: Once
    - Implementation Type: Terraform
-   - Terraform Version: enter what version you used to write the Terraform
+   - OpenTofu Version: enter what version you used to write the OpenTofu
    - Git Repository URL: point this to the Git repository where your Terraform is
    - Git Repository Path: if your Terraform files are under a directory in the repository, enter that path here
    - Git Commit Hash: if you want, enter a Git commit hash so that meshStack will always use the Terraform files at this commit

docs/new-guide-how-to-provide-your-own-platform.md

@@ -47,7 +47,7 @@ Make sure to configure the following details:
 - Supported Platform: select the platform type you created in the previous step.
 - How often assigned: Once
 - Implementation Type: Terraform
-- Terraform Version: enter what version you used to write the Terraform
+- OpenTofu Version: enter what version you used to write the OpenTofu
 - Git Repository URL: point this to the Git repository where your Terraform is
 - Git Repository Path: if your Terraform files are under a directory in the repository, enter that path here
 - Git Commit Hash: if you want, enter a Git commit hash so that meshStack will always use the Terraform files at this commit