Avoid name clashing in ros msg packages

[Affonso-Gui]

Solves #574.

[Affonso-Gui]

#574 (comment)

There are a few possible solutions for this:

• Do not use the lisp package on ros message packages
• Require necessary messages upon loading
• Make sure that the symbol belongs to the designed package during operation

Adopting the first one for simplicity and to avoid re-generating the messages. Since no coding is performed from inside the ros message packages this should have no side effects (tests will confirm that for us).

[Affonso-Gui]

Added test code

[k-okada]

roseus does not depend on jsk_recognition_msgs, so I think it is better to create message for test code, like https://github.com/jsk-ros-pkg/jsk_roseus/pull/509/files.
I also prefer to commit test code first, and confirm the travis failed, then commit the patch (#567)

[Affonso-Gui]

@k-okada Thanks, I was insecure about the previous test code, and the link was of great help.
I added the tests to the existing test-name* tests since

1. Both of them test for name clashing in ros messages
2. Want to avoid having to create new test messages

Test code is also added in #610

[knorth55]

👍 for this PR.

[Affonso-Gui]

@knorth55 Actually we had some test failures and possible bugs here. I'll try to have a look on this week and make any necessary changes to reactivate this