Parse Azure Resource IDs into models

[ranweiler]

In onefuzz.azure.image, for example, we use msrestazure.tools.parse_resource_id() to get a dict representation of the components of an Azure Resource ID. This is very dynamic and weakly-typed, and prone to absent keys in some situations, as a result of the parse_resource_id() function's return type and API.

Instead of doing ad hoc, implicit recognition of what kind of resource we are parsing, we should have models for the resource types we know about, grouped in a Union.

See comment: https://github.com/microsoft/onefuzz/pull/1450/files#r751810404

AB#35946

[Porges]

Won't address this for Python version but have updated the C# version to understand better the resource types that it is handling.

[Porges]

Decided to make it a "proper" discriminated union after all (or as close as we can get to it in C#), since that allows much earlier validation.

[mgreisen]

@Porges has this been addressed then?

[Porges]

@Porges has this been addressed then?

Yes, will close when PR merges.