VSCode Extension v0.12.1 and above - ARM template build adds API version for AutomationAccount

**Bicep version**
v0.12.1 and above - Issue Noted
v0.11.1 and below - working as expected

**Describe the bug**
Bug in VSCode Bicep v0.12.1 and above.
- Related to the nested deployments for Logic Apps in which a webhook is created with an automation account
- Symptoms are that the Logic App will not have the URI populated for the HTTP action as it is returned as null
- Deployment via BICEP file works fine in later versions but the ARM template created has the API version when it should not.
- "Microsoft.Logic/workflows" properties for the URI reference the webhook and include the API version which is considered out of scope and thus a NULL value

These snippets are from my AVD Alerts GitHub Repository:
https://github.com/JCoreMS/AVDAlerts
\deploySubscription\solution.json (Current version is v0.11.1 and working)
- around line 1828

v0.12.1 and above (Not Working)
"uri": "[reference(resourceId('Microsoft.Automation/automationAccounts/webhooks', parameters('AutomationAccountName'), format('{0}_{1}', parameters('RunbookNameGetStorage'), dateTimeAdd(parameters('Timestamp'), 'PT0H', 'yyyyMMddhhmmss'))), **'2018-06-30'**).uri]",

v0.11.1 (Working)
"uri": "[reference(resourceId('Microsoft.Automation/automationAccounts/webhooks', parameters('AutomationAccountName'), format('{0}_{1}', parameters('RunbookNameGetStorage'), dateTimeAdd(parameters('Timestamp'), 'PT0H', 'yyyyMMddhhmmss')))).uri]",

**To Reproduce**
Steps to reproduce the behavior:
Compile BICEP from AVD Alerts or with nested deployments for an Automation Account with VS Code's BICEP extension version 0.12.1 or above incorporating a webhook. When deploying an automation account and runbook with HTTP and using a webhook, the webhook URI isn't captured and thus empty for the URI for the HTTP action in the workflow.

**Additional context**
Add any other context about the problem here.