Auto generated documentation e.g. Markdown and schema

_Originally posted by @Antse in https://github.com/Azure/bicep/discussions/2301#discussioncomment-702665_

by auto generated documentation i mean something like : (must confess i take some example from the official documentation)

Code :

``` bicep
@description('This is the storage account Name')
param stoName string

@description('This is my secure param')
@secure()
param secureParam string

resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
name: stoName // must be globally unique
location: 'eastus'
sku: {
name: 'Standard_LRS'
}
kind: 'StorageV2'
properties: {
supportsHttpsTrafficOnly: true
}
tags: {
'env':secureParam
}
}
```

Doc :

# Deploy a Storage Account

## Overview (global deployed resources schema)

## Parameters

### stoName
- Type
string
- Default value
None
- Description
This is the storage account Name

### secureParam
- Type
secure string
- Default value
None
- Description
This is my Secure Param

## Examples

## Deploy Bicep file to a resource group

**Az CLI**:

```bash
az deployment group create -f ./main.bicep -g my-rg
```

**Azure PowerShell**:

```powershell
New-AzResourceGroupDeployment -TemplateFile ./main.bicep -ResourceGroupName my-rg
```

>**Note:** make sure you update the default value of the `stoName` parameter to be globally unique before deploying.

## Deploy with parameters

Our Bicep file exposed two parameters that we can be optionally overridden (`secureParam` and `stoName`) by passing new values at deployment time.

### Pass parameters on the command line

**Az CLI**:

```bash
az deployment group create -f ./main.bicep -g my-rg --parameters secureParam=MySecretParam stoName=uniquelogstorage001
```

**Azure PowerShell**:

```powershell
New-AzResourceGroupDeployment -TemplateFile ./main.bicep -ResourceGroupName my-rg -location westus -stoName uniquelogstorage001 -secureParam MysecretParam
```

Start with the Bicep example and the proposed Markdown and schema output in the issue, then review the linked discussion for the intended scope. Done should include an agreed approach for generating documentation from Bicep files, covering parameters, resource structure, examples, and deployment commands.

Written by the indexing model from the issue text.