Handle ARM template API profiles

[rjmholt]

From #10:

So based on my current understanding, ARM templates can have an API profile, which is essentially a set of default API versions for resources (but which can be clever when deploying to particular instances of Azure).

This is conceptually simple, although probably some work to implement:

• Have a list of API profiles to complete on
• When resources are passed up to the template level with no API version, we search through the given profile to get the appropriate version and set it
• We need some way of recording and searching API profiles -- this is the labour-intensive part. In particular we need to be able to minimise the amount of servicing we need to do to keep these up to date

[kilasuit]

The Az PowerShell module is looking at a profiling system at the moment

re

We need some way of recording and searching API profiles -- this is the labour-intensive part. In particular we need to be able to minimise the amount of servicing we need to do to keep these up to date

this should be achieveable using the functionality built into the ARM Tools VSCode extension - perhaps there's some code in there that you can depend on or reuse?