Three classes added to allow apps to work as concert apps. They must be refactored together with robot equivalents

Three classes added to allow apps to work as concert apps. They must be refactored together with robot equivalents.

Three classes added to allow apps to work as concert apps. They must be refactored together with robot equivalents
Rename ConcertId as MasterId; it should replace also RobotId, but it's gonna imply a lot of renaming, so we must plan in advance.
Additional convenience constructor taking all attributes
Concertify
Starting fussion of concert/robot apps
Use rocon_std_msgs messages and services
Final solution to the Robot/Concert/Master Description dilema: iherit from MasterDescription
Concertified teleop working
Issue #31: replace robot id by master id
Issue #31: Renamed from ConcertAppActivity. Fully working but not fully tested.
We don't need anymore to cast to Robot/Concert Description, so we can move these classes somewhere else, if we want
Issue #31: Need parameter-less constructor so can be parsed by snakeyaml
Working version.
Just comments
Issue #31: replace robot name by master name
Issue #31: Replaced bu MasterId
Simple class to provide a get method with default value to LinkedHashMap
Use new params and remaps container classes
Remove RemoconURI, as it is also in the MasterDescription
Read all intent's content in one method (both init methods reorganized)
Teleop migrated to the paired/concert common frame:
 - RosAppActivity is master neutral, no robot-centered
 - Remocon provides parameters and remaps lists
Map_nav migrated to the paired/concert common frame:
 - RosAppActivity is master neutral, no robot-centered
 - Remocon provides parameters and remaps lists
According to changes in app manager (https://github.com/robotics-in-concert/rocon_app_platform/issues/107), remove 'application' namespace
Listener migrated to the paired/concert common frame:
 - RosAppActivity is master neutral, no robot-centered
 - Remocon provides parameters and remaps lists