using deployment().properties.templateLink.uri in bicep

[bmoore-msft]

Related to #27

Staging of templates will be unnecessary in bicep since we compile and send inline. A couple things came to mind:

1. common pattern in ARM today is to use deployment().properties.templateLink.uri as a "root" location for all artifacts (templates and non-template files). This property only exists when the deployment resource is created with a templateLink property. If we send inline, this won't exist and the pattern won't work.

2. should the CLIs do staging to solve the problem (and just first class the scenario in general) what happens for non-cli users?

[alex-frankel]

Are these concerns specifically for non-template artifacts? Won't the template link property still exist as long as I deploy the main template via uri?

If this is specifically about non-template artifacts, then yes I do think we should first class this as much as we can. As with template specs, I think the experience will be best with the CLIs, but the APIs the CLI depends on should also be as easy to use as possible.

[alex-frankel]

This will become more of a concern when deployment tooling is compiling bicep and creating the deployment. For now, we can instruct them to deploy however it is required