[DOCS] Adding Markdown file for spk deployment create (#7)

* Added create.md

* Update

* Adding command examples about other pipelines

Co-authored-by: Dennis Seah <dennis.seah@gmail.com>
Co-authored-by: Yvonne Radsmikham <yvonne.radsmikham@gmail.com>
Co-authored-by: Samiya Akhtar <samiyaakhtar7@gmail.com>

docs/commands/data.json

@@ -94,7 +94,8 @@
         "arg": "--repository <repository>",
         "description": "URL of the repository (SRC, HLD, Manifest)"
       }
-    ]
+    ],
+    "markdown": "## Description\n\nThis command inserts data about pipeline runs into Azure Table storage.\n\n## Example\n\nThe following command has parameters for Azure Table storage credential and\nvarious pipelines run details.\n\n```\nspk deployment create  -n $AZURE_STORAGE_ACCOUNT_NAME \\\n    -k $AZURE_ACCOUNT_KEY \\\n    -t $AZURE_TABLE_NAME  \\\n    -p $AZURE_TABLE_PARTITION_KEY \\\n    --p2 $(Build.BuildId) \\\n    --hld-commit-id $latest_commit \\\n    --env $(Build.SourceBranchName) \\\n    --image-tag $tag_name \\\n    --pr $pr_id \\\n    --repository $repourl\n```\n"
   },
   "deployment dashboard": {
     "command": "dashboard",
@@ -237,7 +238,7 @@
     "command": "append-variable-group <variable-group-name>",
     "alias": "avg",
     "description": "Appends the name of an existing variable group to the current manifest-generation.yaml file.",
-    "markdown": "## Description\n\nAppend a variable group name to the current `manifest-generation.yaml` of an\ninitialized hld repository.\n\n## Example\n\nWhen an HLD repository is first initialized with `spk hld init`, the top portion\nof the `manifest-generation.yaml` looks like this:\n\n```yaml\n# GENERATED WITH SPK VERSION 0.5.8\ntrigger:\n  branches:\n    include:\n      - master\nvariables: []\npool:\n  vmImage: ubuntu-latest\nsteps:\n.\n.\n.\n```\n\nrunning `spk hld append-variable-group my-vg` with a variable group name, in\nthis case `my-vg`, will add it under the `variables` section if it does not\nalready exist:\n\n```yaml\n# GENERATED WITH SPK VERSION 0.5.8\ntrigger:\n  branches:\n    include:\n      - master\nvariables:\n  - group: my-variable-group\npool:\n  vmImage: ubuntu-latest\nsteps:\n.\n.\n.\n```\n"
+    "markdown": "## Description\n\nAppend a variable group name to the current `manifest-generation.yaml` of an\ninitialized hld repository.\n\n## Example\n\nWhen an HLD repository is first initialized with `spk hld init`, the top portion\nof the `manifest-generation.yaml` looks like this:\n\n```yaml\ntrigger:\n  branches:\n    include:\n      - master\nvariables: []\npool:\n  vmImage: ubuntu-latest\nsteps:\n.\n.\n.\n```\n\nrunning `spk hld append-variable-group my-vg` with a variable group name, in\nthis case `my-vg`, will add it under the `variables` section if it does not\nalready exist:\n\n```yaml\ntrigger:\n  branches:\n    include:\n      - master\nvariables:\n  - group: my-variable-group\npool:\n  vmImage: ubuntu-latest\nsteps:\n.\n.\n.\n```\n"
   },
   "hld init": {
     "command": "init",

src/commands/deployment/create.md

@@ -0,0 +1,43 @@
+## Description
+
+This command inserts data about pipeline runs into Azure Table storage.
+
+## Example
+
+The following command has parameters for Azure Table storage credential and various pipelines run details. It's used by the source build pipeline, the release stage and the manifest generation pipeline, and each of them pass in parameters depending on the information for that pipeline. Here are three examples: 
+
+```
+spk deployment create  -n $AZURE_STORAGE_ACCOUNT_NAME \
+    -k $AZURE_ACCOUNT_KEY \
+    -t $AZURE_TABLE_NAME  \
+    -p $AZURE_TABLE_PARTITION_KEY \ 
+    --p1 $(Build.BuildId) \
+    --image-tag $tag_name \
+    --commit-id $commitId \
+    --service $service \
+    --repository $repourl
+```
+
+```
+spk deployment create  -n $AZURE_STORAGE_ACCOUNT_NAME \
+    -k $AZURE_ACCOUNT_KEY \
+    -t $AZURE_TABLE_NAME  \
+    -p $AZURE_TABLE_PARTITION_KEY \ 
+    --p2 $(Build.BuildId) \
+    --hld-commit-id $latest_commit \
+    --env $(Build.SourceBranchName) \
+    --image-tag $tag_name \
+    --pr $pr_id \
+    --repository $repourl
+```
+
+```
+spk deployment create  -n $AZURE_STORAGE_ACCOUNT_NAME \
+    -k $AZURE_ACCOUNT_KEY \
+    -t $AZURE_TABLE_NAME  \
+    -p $AZURE_TABLE_PARTITION_KEY \ 
+    --p3 $(Build.BuildId) \ 
+    --hld-commit-id $commitId \ 
+    --pr $pr_id \
+    --repository $repourl
+```

src/commands/hld/append-variable-group.md

@@ -9,7 +9,6 @@ When an HLD repository is first initialized with `spk hld init`, the top portion
 of the `manifest-generation.yaml` looks like this:
 
 ```yaml
-# GENERATED WITH SPK VERSION 0.5.8
 trigger:
   branches:
     include:
@@ -28,7 +27,6 @@ this case `my-vg`, will add it under the `variables` section if it does not
 already exist:
 
 ```yaml
-# GENERATED WITH SPK VERSION 0.5.8
 trigger:
   branches:
     include: