Add pipelines settings content, missing icons

Author: ZachGoldberg

docs/2.0/docs/pipelines/configuration/settings.md

@@ -1,10 +1,12 @@
 # Pipelines Configuration
 
-This page is under construction.  In the mean time, checkout the [Pipelines Configuration Reference Page](/docs/2.0/reference/pipelines/configurations.md) for a list of all available configuration options.
+[Full Pipelines Configuration Reference](/docs/2.0/reference/pipelines/configurations.md)
 
+import PipelinesConfig from '/docs/2.0/reference/pipelines/language_auth_partial.mdx'
 
-<!--
-e.g. TF vs Tofu, deploy branch name etc.
-This is different from reference content because we can also add a few extra paragraphs explaining things, not just a raw list
+<PipelinesConfig />
 
--->
+
+## Terraform & OpenTofu
+
+You can customize whether to invoke Terraform or OpenTofu in your Pipeline via the [tf-binary](/2.0/reference/pipelines/configurations#tf-binary) configuration. The version of the `tf-binary` and Terragrunt are configured via [mise.toml](/2.0/reference/pipelines/configurations#example-mise-configuration) inside your repository

docs/2.0/reference/pipelines/index.md

@@ -1,22 +1,8 @@
 # Overview
 
-## Configuration Language Transition
+import PipelinesConfig from './language_auth_partial.mdx'
 
-Pipelines configurations are currently undergoing a transition from YAML configurations to new HCL [Configurations as Code](./configurations-as-code.md). These new configurations will offer a richer configuration experience, but are not yet required for use. [YAML configurations](./configurations.md) will continue to work as expected for the time being.
-
-YAML configurations are read by Pipelines when HCL configurations are not present, and the Pipelines binary falls back to interpretting YAML configurations as if they were defined in the HCL configuration system in this scenario.
-
-This means that if you have a `.gruntwork/config.yml` file in your repository, you can continue to use it as you have been, and Pipelines will continue to work as expected.
-
-If you do introduce any HCL configurations into your `.gruntwork` directory or introduce a `gruntwork.hcl` file into a directory, Pipelines will begin to use the HCL configuration system instead of the YAML configuration system.
-
-## Authentication
-
-Core pipelines functionally generally requires only a small amount of configuration.  The most critical configuration for the CI/CD pipeline is how to authenticate with AWS, and that is covered in one of two ways:
-
-* With the YAML system pipelines expects each top-level folder in the repository to correspond to an account in `accounts.hcl` and the existance of appropriate OIDC roles to enable pipeliens to assume the respective role for infra changes in those folders.  As such, very little of the YAML configuration requires customization.
-
-* With the HCL system users can flexibly configure pipelines to authenticate to various AWS accounts to match arbitrary folder structures.  The bulk of the HCL configuration language we define is to support this flexibility.
+<PipelinesConfig />
 
 ## Other Configuration
 

docs/2.0/reference/pipelines/language_auth_partial.mdx

@@ -0,0 +1,17 @@
+## Configuration Language Transition
+
+Pipelines configurations are currently undergoing a transition from YAML configurations to new HCL [Configurations as Code](./configurations-as-code.md). These new configurations will offer a richer configuration experience, but are not yet required for use. [YAML configurations](./configurations.md) will continue to work as expected for the time being.
+
+YAML configurations are read by Pipelines when HCL configurations are not present, and the Pipelines binary falls back to interpretting YAML configurations as if they were defined in the HCL configuration system in this scenario.
+
+This means that if you have a `.gruntwork/config.yml` file in your repository, you can continue to use it as you have been, and Pipelines will continue to work as expected.
+
+If you do introduce any HCL configurations into your `.gruntwork` directory or introduce a `gruntwork.hcl` file into a directory, Pipelines will begin to use the HCL configuration system instead of the YAML configuration system.
+
+## Authentication
+
+Core pipelines functionally generally requires only a small amount of configuration.  The most critical configuration for the CI/CD pipeline is how to authenticate with AWS, and that is covered in one of two ways:
+
+* With the YAML system pipelines expects each top-level folder in the repository to correspond to an account in `accounts.hcl` and the existance of appropriate OIDC roles to enable pipeliens to assume the respective role for infra changes in those folders.  As such, very little of the YAML configuration requires customization.
+
+* With the HCL system users can flexibly configure pipelines to authenticate to various AWS accounts to match arbitrary folder structures.  The bulk of the HCL configuration language we define is to support this flexibility.