split basic_move_controller and navigator into separate nodes

[bit-pirate]

The basic_move_controller does not seem to be used inside the navigator, but only is made available through it.

Hence, I suggest to put the basic move controller into it's own node, so it can be started when needed.

@jihoonl what do you think?

[jihoonl]

basic_move_controller is already independent library from navigator. So it can be used without navigator.

I considered to have basic_move_controller as independent package though. But I couldn't find any good reason to make it as independent. I kept them together with these reasons.

• It is used in semantic_navigator.
• It is still available as independent library.
• It prevents # of package explosion. We already have enough number of packages to maintain.

Thus, I suggest to keep them together until we find strong desire to make them separate.