dropping namespace package

[asmodehn]

Although quite practical to allow us to retrieve catkin generated messages even without sourcing ROS setup, it will prevent us from making a working ROS package for this (tested with pyros-dev/pyros-common#1).

So we need to turn this into a normal package, while keeping all our usecases working :

• from ROS (full catkin usecase)
• from python isolated in venv (tox usecase)
• from python on top of ROS system (PyCharm running tests on ROs machine usecase)...

[asmodehn]

The tentative release 0.1.1 still has a namespace package definition...

[asmodehn]

Since rosimport, the python user is expected to use it, OR the usual ROS catkin system, to generate message python code.
Therefore generating the python code is not the responsibility of this package any longer, and we should be able to drop the namespace package declaration, and everything should still work as expected.

[asmodehn]

namespace has been dropped in #14 however this might create problems with catkin, since messages will be created in another folder (in devel and not in source), and with python2 namespace package is needed to unify both in same package...
We need to test this more.

[asmodehn]

Closing since PR has been merged. If problems arise, they can be flagged as separate issues.