Output type inference

[jeskew]

Addresses an ask from #10354

As a companion to #10418, this PR updates output type inference to take the supplied output value into account.

One potential drawback of inferring more detailed type information from the value is that while Bicep can easily figure out an extremely narrow type for a statement written in Bicep, the compiler isn't as smart when looking at JSON templates. E.g., the type of foo would be 'foo' in output foo string = 'foo' and would just be string in:

{
  ...
  "outputs": {
    "foo": {
      "type": "string",
      "value": "foo"
    }
  }
}

The above limitation would mean that type inference would work for a local bicep module but not one that had been published to the registry.

Microsoft Reviewers: Open in CodeFlow

[jeskew]

Per a team discussion, publishing a Bicep module to a registry should not be a lossy proposition. Inferred type information would need to be persisted in the compiled JSON template.