docs: move docker and container documentation to top-level page (#634)

## 📝 Description
Move the documentation of Docker and Containers to the top level page in
the sidebar. Reorganizes information about Docker and Container in one
place so it's easy to find and search.

Addresses #630

## ✅ Checklist
- [X] I have tested this change
- [ ] This change requires documentation update

Author: TomFern

docs/docs/reference/pipeline-yaml.md

@@ -2,7 +2,7 @@
 description: Pipeline YAML reference
 ---
 
-# Pipeline YAML 
+# Pipeline YAML
 
 This page describes the formal pipeline YAML specification for Semaphore.
 
@@ -43,7 +43,7 @@ Defines the global agent's [`machine` type](#machine) and [`os_image`](#os-image
 The `agent` can contain the following properties:
 
 - [`machine`]: VM machine type to run the jobs
-- [`containers`]: optional Docker containers to run the jobs
+- [`containers`](#containers): optional Docker containers to run the jobs
 
 ```yaml title="Example"
 # highlight-next-line
@@ -61,7 +61,7 @@ The default `agent` can be overridden [inside `tasks`](#agent-in-task).
 
 ### machine {#machine}
 
-Part of the [`agent`](#agent) definition. It defines the global VM machine type to run the jobs. 
+Part of the [`agent`](#agent) definition. It defines the global VM machine type to run the jobs.
 
 It requires two properties:
 
@@ -108,7 +108,7 @@ machine:
 
 ## containers {#containers}
 
-An optional part of [`agent`](#agent). Defines an array of Docker image names to run jobs. 
+An optional part of [`agent`](#agent). Defines an array of Docker image names to run jobs.
 
 The first container in the list runs the jobs. You may optionally add more items that run as separate containers. All containers can reference each other via their names, which are mapped to hostnames using DNS records.
 
@@ -252,6 +252,7 @@ agent:
 Defines an optional time limit for executing the pipeline. Jobs are forcibly terminated once the time limit is reached. The default value is 1 hour.
 
 The `execution_time_limit` property accepts one of two options:
+
 - `hours`: time limit expressed in hours. Maximum value is 24
 - `minutes`: The time limit is expressed in minutes. The maximum value is 1440
 
@@ -400,7 +401,7 @@ The following rules apply:
 
 When `scope: project` the queues with the same values for the `name` property in different projects are not queued together.
 
-When `scope: organization` the pipelines from the queue will be queued together with pipelines from other projects within the organization that have a queue configuration with the same `name` and `scope` values. 
+When `scope: organization` the pipelines from the queue will be queued together with pipelines from other projects within the organization that have a queue configuration with the same `name` and `scope` values.
 
 The `processing` property can have two values:
 
@@ -428,7 +429,6 @@ Sets a strategy for auto-canceling pipelines in a queue when a new pipeline appe
 
 At least one of them is required. If both are set, `running` will be evaluated first.
 
-
 ### running {#running-in-auto-cancel}
 
 When this property is set, queued and running pipelines are canceled as soon as a new workflow is triggered. This property requires a `when` property that defines a condition according to [Conditions DSL](./conditions-dsl).
@@ -801,7 +801,6 @@ The indentation level of the `prologue`, `epilogue`, `env_vars`, and `jobs` prop
 
 :::
 
-
 ### prologue {#prologue-in-task}
 
 A `prologue` block in a `task` block is used when you want to execute certain commands prior to the commands of each job of a given `task`. This is usually the case with initialization commands that install software, start or stop services, etc.
@@ -911,7 +910,7 @@ The location of the file is relative to the pipeline file. For example, if your
 
 ### secrets {#secrets-in-task}
 
-A [secret](../using-semaphore/secrets) is a place for keeping sensitive information in the form of environment variables and small files. Sharing sensitive data in secret is both safer and more flexible than storing it using plain text files or environment variables that anyone can access. 
+A [secret](../using-semaphore/secrets) is a place for keeping sensitive information in the form of environment variables and small files. Sharing sensitive data in secret is both safer and more flexible than storing it using plain text files or environment variables that anyone can access.
 
 The `secrets` property is used for importing all the environment variables and files from an existing secret into a Semaphore organization.
 
@@ -1181,7 +1180,6 @@ The following environment variables are added to each generated job:
 - `SEMAPHORE_JOB_COUNT`: total number of jobs generated via the `parallelism` property
 - `SEMAPHORE_JOB_INDEX`: value in the range from `1` to `SEMAPHORE_JOB_COUNT`, which represents the index of a particular job in the list of generated jobs.
 
-
 ```yaml title="Example"
 version: v1.0
 name: Using the parallelism property
@@ -1201,14 +1199,14 @@ blocks:
             - echo Job $SEMAPHORE_JOB_INDEX out of $SEMAPHORE_JOB_COUNT
             - make test PARTITION=$SEMAPHORE_JOB_INDEX
 ```
+
 It will automatically create 4 jobs with the following names:
 
 - `Parallel job - 1/4`
 - `Parallel job - 2/4`
 - `Parallel job - 3/4`
 - `Parallel job - 4/4`
 
-
 :::note
 
 It is not possible to have both `parallelism` and [`matrix`](#matrix-in-jobs) properties defined for the same job, as `parallelism` functionality is a subset of `matrix` functionality.
@@ -1495,7 +1493,6 @@ blocks:
 
 All the displayed files are correct pipeline YAML files that could be used as `semaphore.yml` files.
 
-
 ### result {#result-in-promotions}
 
 The value of the `result` property is a string that is used for matching the status of a pipeline.
@@ -1714,10 +1711,9 @@ The following functions are supported. Refer to the [Sprout documentation](https
 </div>
 </details>
 
-
 ### Pipeline name {#parameter-pipeline-name}
 
-The following example customizes the pipeline name given the parameters `DEPLOY_ENV` and `SERVER`. 
+The following example customizes the pipeline name given the parameters `DEPLOY_ENV` and `SERVER`.
 
 ```yaml title="deploy.yml"
 version: v1.0
@@ -1816,7 +1812,6 @@ blocks:
                 commands: ./deploy.sh
 ```
 
-
 ### Global config {#parameter-global}
 
 You can use parameters in the [global config](#global-job-config) for the pipeline.
@@ -1841,7 +1836,6 @@ global_job_config:
 
 The following example shows how to dynamically assign pipelines to [names queues](../using-semaphore/pipelines#named-queues) with parameters.
 
-
 ```yaml title="deploy.yml"
 version: v1.0
 name: Deployment pipeline
@@ -1885,7 +1879,6 @@ blocks:
 
 You can define a [job matrix](../using-semaphore/jobs#matrix) with parameters. Given `AWS_REGIONS=us-central-1,us-east1`, the following example runs the `deploy.sh` script both regions by transforming the comma-separated regions in a YAML list.
 
-
 ```yaml title="deploy.yml"
 version: v1.0
 name: Deployment pipeline
@@ -2037,7 +2030,6 @@ The `auto_promote_on` property is a list of items that supports three properties
 
 For an `auto_promote_on` branch to execute, the return values of all the used properties of that branch must be `true`.
 
-
 <details>
 <summary>`auto_promote_on` example</summary>
 <div>
@@ -2141,7 +2133,6 @@ Both `p1.yml` and `p2.yml` are correct pipeline YAML files that could be used as
 </div>
 </details>
 
-
 ## Complete examples {#complete-examples}
 
 This section shows complete pipelines showcasing YAML features.
@@ -2206,7 +2197,6 @@ blocks:
 <summary>Pipeline using secrets</summary>
 <div>
 
-
 ``` yaml
 version: v1.0
 name: Pipeline configuration with secrets
@@ -2260,7 +2250,6 @@ blocks:
 </div>
 </details>
 
-
 ## See also
 
 - [Jobs YAML reference](./jobs-yaml)
@@ -2270,4 +2259,3 @@ blocks:
 - [Agents YAML reference](./agent-yaml)
 - [Notifications YAML reference](./notifications-yaml)
 - [Semaphore Command Line reference](./semaphore-cli)
-