ng deploy

Hi! 👋

Firstly, thanks for your work on this project! 🙂

Today I used [patch-package](https://github.com/ds300/patch-package) to patch `@azure/ng-deploy@0.2.3` for the project I'm working on.

Here is the diff that solved my problem:

```diff
diff --git a/node_modules/@azure/ng-deploy/out/ng-add/schema.json b/node_modules/@azure/ng-deploy/out/ng-add/schema.json
index 8d84a0a..086381c 100644
--- a/node_modules/@azure/ng-deploy/out/ng-add/schema.json
+++ b/node_modules/@azure/ng-deploy/out/ng-add/schema.json
@@ -1,6 +1,6 @@
{
"$schema": "http://json-schema.org/schema",
- "id": "azure-deploy-schematic-ng-add",
+ "$id": "azure-deploy-schematic-ng-add",
"title": "Azure Deploy ng-add schematic",
"type": "object",
"properties": {
```

This issue body was [partially generated by patch-package](https://github.com/ds300/patch-package/issues/296).

Start by inspecting node_modules/@azure/ng-deploy/out/ng-add/schema.json and the ng-add schematic entry point mentioned by the package path. Confirm the schema metadata uses "$id" rather than "id", then verify that ng deploy can consume the corrected schema without the reported patch.

Written by the indexing model from the issue text.