Move templates to official v2 schema

[ejizba]

Templates for the v4 model are currently hard-coded in tooling and also don't match the official v2 schema. They are using a schema I'll call v1.1, which was a temporary workaround to get these working before the v2 schema was finalized. The v1.1 schema was something I came up with and the goal was to minimize the changes from v1 while still fully supporting the new model templates at parity with the old model. By comparison, the v2 schema is way different than the v1 schema so moving to that schema (once it was finalized) was more complicated.

v1.1 schema

Hard-coded location of v1.1 schema templates:

• VS Code: https://github.com/microsoft/vscode-azurefunctions/tree/main/resources/backupTemplates/nodejs-4.x
• Core Tools: https://github.com/Azure/azure-functions-core-tools/blob/v4.x/src/Azure.Functions.Cli/StaticResources/node-v4-templates.json
• Portal: Not supported by the new model
• VS: Not supported for Node.js

Here is the custom logic to support the v1.1 schema (just as an fyi):

• VS Code
  • https://github.com/microsoft/vscode-azurefunctions/blob/main/src/commands/createFunction/scriptSteps/NodeV4FunctionCreateStep.ts
  • https://github.com/microsoft/vscode-azurefunctions/blob/main/src/commands/createFunction/scriptSteps/NodeV4FunctionNameStep.ts
• Core Tools. The main difference is core tools doesn't support prompting for binding info (http auth level, timer schedule, blob path, etc.).
  • https://github.com/Azure/azure-functions-core-tools/blob/v4.x/src/Azure.Functions.Cli/Common/TemplatesManager.cs#L141

v2 schema

I worked on updating templates to the v2 schema, but we abandoned the effort after we decided we weren't going to support the portal.

• Branch: https://github.com/Azure/azure-functions-templates/tree/ej/nodejsv4
• PR: Add Node.js model v4, schema v2 templates azure-functions-templates#1412