Move usage examples into docs section

Author: Bi0T1N

docs/input/docs/usage/cli/output.md

@@ -21,3 +21,17 @@ For that you have to run `GitVersion.exe /output dotenv` and store the output
 into e.g. a `gitversion.env` file. These files can also be passed around in CI environments
 like [GitHub](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#passing-values-between-steps-and-jobs-in-a-workflow)
 or [GitLab](https://docs.gitlab.com/ee/ci/variables/#pass-an-environment-variable-to-another-job).
+Below are some examples of using the Dotenv format in the Unix command line:
+```bash
+# Output version variables in Dotenv format
+gitversion /output dotenv
+
+# Show only a subset of the version variables in Dotenv format
+gitversion /output dotenv | grep -i "prerelease"
+
+# Show only a subset of the version variables that match the regex in Dotenv format
+gitversion /output dotenv | grep -iE "major|sha=|_prerelease"
+
+# Write version variables in Dotenv format into a file
+gitversion /output dotenv > gitversion.env
+```

new-cli/command.md

@@ -53,18 +53,6 @@ cat gitversion.json | gitversion output buildserver
 # Read version variables from stdin and write to Jenkins.
 cat gitversion.json | gitversion output buildserver --buildserver Jenkins
 
-# Output version variables in Dotenv format
-gitversion /output dotenv
-
-# Show only a subset of the version variables in Dotenv format (Unix syntax)
-gitversion /output dotenv | grep -i "prerelease"
-
-# Show only a subset of the version variables that match the regex in Dotenv format (Unix syntax)
-gitversion /output dotenv | grep -iE "major|sha=|_prerelease"
-
-# Write version variables in Dotenv format into a file
-gitversion /output dotenv > gitversion.env
-
 # Read version variables from stdin and write to globbed .wxi files.
 cat gitversion.json | gitversion output wix --path ./**/*.wxi