wadm shouldn't operate components & providers started elsewhere

[lxfontes]

Right now wadm assumes to be the only orchestrator responsible for placing components & providers on host.
That assumption is not true.

wadm should only manipulate components & providers related to "wadm models".

Suggestion: rely on the annotations field to determine if a component/provider is being managed by wadm.

Bonus points: consider the situation where multiple wadms are running on the same lattice ( meaning the annotation should also carry a wadm-id )

[brooksmtownsend]

@lxfontes do you have some sample reproduction steps for this? If wadm is removing components/providers that do not have the wadm annotation, then it is a bug.