in #using_task_library, only assume that +name+ is an orogen file if it ends in .orogen

This fixes a problem where

  using_task_library "bla"

would load the *file* bla if one is present in the current directory,
instead of loading the oroGen project called 'bla'.
spec: define #orocos_type_name on Port and ConfigurationObject

Base types on the RTT side are non-normalized and cannot therefore
be accessed using the typelib types. Provide a generic function to
do the mapping, and define #orocos_type_name on Port and Property
to get the "right" type name
spec: in merge_ports_from, provide more specific errors if the ports cannot be merged
gen: check for stray dots only if the project has a definition file

In test cases, projects do not have a definition file and an error
in check_for_stray_dots is then hiding actual errors.
remove the deployment from the generated orogen file, we don't need those anymore
ros: start a ROS transport

This first step generates messages from oroGen types and properly
compiles them on fuerte (I don't plan to support earlier ROS versions
as they would require rosbuild to be around).
ros: don't generate messages for the m-types
ros: make good use of CMAKE_PREFIX_PATH

catkin is using CMAKE_PREFIX_PATH as a way to register lots of
packages in one shot, so just use it instead of adding bad hacks
ros: generate the full ROS transport

The transport plugin is an adaptation of the CORBA transport plugin.

So far, only the toROS / fromROS functions need to be filled (they
are currently empty)
ros: don't put any special handling for base::Time

This is going to be handled by the convertion-to-existing-messages
features
ros: fix what should / should not be exported to ROS
ros: rename ROSTransportPlugin to RosTransportPlugin to follow the convention that oroGen expects in deployments
ros: properly handle the case where no messages are generated
ros: fix package name of dependencies in the generate message calls
ros: add dependencies of transporters on the message generation
ros: fix multi-line split
ros: properly link to our dependencies
ros: fix deployments when using ros

We must call ros::init and such
ros: fix basic type handling
fix Typekit#m_type? for types that depend on m-types