Add new type of component which is just the VAPSets

[AJamesPhillips]

Currently

• Another user can not take a publicly readable, non-writable component with VAPSets and overwrite the VAPsets on it.

Description (acceptance criteria)

• [ ] This component will have an attribute target_wcomponent (where the component has VAPSets)
• [ ] When in the knowledge view it will behave similarly to a counterfactual and override the target component's VAPsets
• [ ] It will not be allowed to be the target of a counterfactual. If you want to apply a counterfactual to a wcomponent which has itself been the target of a VAPSet replacement you can use the "Move to front" button so that the counterfactual is applied last? you do not need to do anything special as the VAP set replacement happens before the counterfactuals are applied.

Why (hypothesis)

• Will allow for classes and overriding with values
• Will allow for the perceptions to be first classed, i.e. can be used as causes & effects, can be related to others, can be labelled, can be associated with actions

Alternatives you've considered

Additional context

Perhaps we need to rename counterfactuals as this new VAPSet component is actually a type of complex counterfactual.

[AJamesPhillips]

This is completed with the addition of the state_value type component: 157a1e79