Loose objects with strong views

[davidfowl]

• This fundamentally changes the resource model to be all in on annotations. Resources are a set of annotatations and strongly typed "views" can be modeled over those annotations. Each resource has a ResourceTypeAnnotation which stores the actual resource type. This means that runtime code should never use is or as for resource type checks but should instead use the new ResourceKind API to determine the type of the resource.
• This enables cleanly switching between resource types while keeping the veneer of strong typing at the top level.

TODO:

• Update tests

Issues found:

• We still need to design resources intentionally when want the ability to apply thier configuration to another resource. e.g. RunAsContainer for AzureRedis -> Redis container. This is trivial to do with the change, but doesn't solve the we need to duplicate the logic to configure redis.
• Identity, the identity of the underlying resource needs to be based on the annotation collection, not the object instance.

[davidfowl]

@eerhardt I don't think this will be the final API shape but the idea here is to get the redis defaults applied to an existing builder.

[eerhardt]

We don't expect "normal" customers to call this method right? Maybe it shouldn't be an extension method so it doesn't clutter up the Intellisense for normal AppHost developers.