Remove support for component type specific child attributes

[ml019]

Expected Behaviour

The type of a component should be controlled via a mandatory Type attribute. With this in place, there is no requirement for type specific child attributes. Thus these can be removed and the overall depth of a hamlet solution reduced.

Similarly for links, the selection of subcomponents should be achieved via the use of the Subcomponent attribute and support for the component specific attributes removed. The Type attribute should also be used for resolution of any link conflicts to identically named subcomponents, and also to set the expectation of the target of the link.

Current Behaviour

The type can be specified either through the Type attribute or via specifically named child attributes.

Similarly links support both the Subcomponent attribute and subcomponent type specific attributes.

Possible Solution

• change the component type detection local to rely solely on the Type attribute
• change the link subcomponent target specification to be the Subcomponent attribute
• would require all solutions to be upgraded to use this approach - hence the need for a breaking version

Context

• reduce the nesting required in a solution file
• remove the need to constantly extent the schema for links
• provide consistency and "one way of doing things"
• enable the use of more advanced JSON schema techniques where content can be driven off the value of an attribute