Support float values

[miqm]

Follow up from #486

We need to add support for floating point values that can be entered by user.
Floating point values - numbers with dot i.e. 3.14 have following constraints:

• Float values can be entered manually only in the code as a variable or object value
• They cannot be a parameter
• They cannot be an output of an function
• They are not allowed as part of expressions
• There's float() function that should be supported - it can be used only in variables and as object values

Valid usage in ARM:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "inPi": {
      "type": "string",
      "defaultValue": "3.14"
    }
  },
  "functions": [],
  "variables": {
    "pi": 3.14,
    "objectPi": {
      "pi": 3.14
    },
    "pi2": "[float('3.14')]",
    "pi3": "[float(variables('pi'))]",
    "pi4": "[float(parameters('inPi'))]"
  },
  "resources": [],
  "outputs": {
    "out0": {
      "type": "object",
      "value": "[createObject('pi', variables('pi'))]"
    },
    "out1": {
      "type": "object",
      "value": "[variables('objectPi')]"
    },
    "out2": {
      "type": "object",
      "value": "[createObject('pi2',variables('pi2'))]"
    },
    "out3": {
      "type": "object",
      "value": "[createObject('pi3',variables('pi3'))]"
    },
    "out4": {
      "type": "object",
      "value": "[createObject('pi4',variables('pi4'))]"
    }
  }
}

[kopendrex]

Problem with the floating point is in the 'Microsoft.ContainerInstance/containerGroups' too, there is validation error during try set 0.5 memory
resources:{ requests:{ cpu: 1 memoryInGB: 0.5 } }

[miqm]

@alex-frankel perhaps we can shift this to v0.3?

[alex-frankel]

No objections to doing this sooner, but @miqm I think there are more pressing needs for 0.3. Do you think you could pick up either of these?

Obviously, no worries if you'd rather not pick those up and focus on items that are more appealing to you. LMK.

[majastrz]

Yeah, I'm not sure there's an agreed upon design for this issue yet. Also, @TarunSunkaraneni picked up the output file location one.

[miqm]

Ok, then I'll take the key vault issue.

[anthony-c-martin]

If anyone runs into this, the workaround for now is to use the json() function with a string representation of your float value, so where you would want to write 3.14, instead write json('3.14').

e.g.:

var pi = json('3.14')

output out0 object = {
  pi: pi
}