Add drop point controller

[brothercorvo]

No description provided.

[naman108]

This branch is an initial attempt to implement a component to manage the logic for drop point operations. This functionality would probably be a good candidate for testing the new OAS based component generator. @brothercorvo it would be useful if you could write up a brief description of it's expected functionality in this PR so we know what the purpose is.

[brothercorvo]

Not sure that this is a separate component, probably a controller of the existing one

[naman108]

Not sure that this is a separate component, probably a controller of the existing one

maybe make this apart of the CoTManagerComponent? In any case we still need a clear idea of what it should do, I was thinking this may be related to issue #627. Maybe this component/controller could provide the crud functionalities for the API?

[brothercorvo]

CoTManager is what I WAS REFERRING TO.
we need also the COTManager to use the new blue print infrastructure and be able to save different types of CoT to persistency. this would solve #627

[naman108]

CoTManager is what I WAS REFERRING TO. we need also the COTManager to use the new blue print infrastructure and be able to save different types of CoT to persistency. this would solve #627

cool, then let's get #675 sorted out and then create a branch for this.

[brothercorvo]

the idea of this code is to evaluate a 'COT' aka Marker aka drop point and to react differently depending from the type and attitude, this is a crucial FTS functionality @naman108