test_roscpp: added unit test for calling zombie services, see #434

Zombie services are left behind by crashed nodes. Currently roscpp can
lock up when you call such a zombie service.
test_roscpp: service_call_zombie: reduce service call count

This makes the test faster if it passes.
roscpp: Connection: emit drop_signal_ after unlocking drop_mutex_

Callbacks connected to the signal might want to lock other things, which
will violate lock ordering and probably cause a deadlock.

Moving the call out of the protected section is not dangerous, since
the connection is only dropped once.
roscpp: ServiceManager: initialize connection before connecting, fixes #434

This makes sure that the drop callback is registered before the connect
occurs. Previously it was possible to loose the drop event and cause a
freeze of the current thread.
Fix typo in rosbag usage
Merge pull request #447 from lrasinen/indigo-devel

Fix typo in rosbag usage
fix typo in variable name set by param
Merge branch 'indigo-devel' of https://github.com/ros/ros_comm into indigo-devel
Merge pull request #448 from andreasBihlmaier/indigo-devel

fix typo in variable name set by param
Merge pull request #435 from xqms/zombie_lockup

test_roscpp: added unit test for calling zombie services, see #434
convert to use console bridge from upstream debian package (ros/rosdistro#4633)
update changelogs
1.11.5
fix unit test to reflect 3rdparty status of console_bridge
Add respawn_delay parsing and storage

Modify parser and all relevant classes to keep track of optional
respawn_delay. No behavioral changes.
Track time of node shutdown

Record the first time which is_alive() returns False. Using this
as time_of_death assumes is_alive is being polled, fortunately this
is exactly what ProcessMonitor does.
time_of_death is initialized to None and reset to None on node startup
respawn after a configurable delay

Keep a list of nodes which have exited and whos respawn_delay has not yet
passed. Check the list each time through the process monitoring loop, restarting
nodes as their delay expires.
Move time_of_death handling up to Process class

I had this in LocalProcess, base on the testing architecture it looks
like it should go here.
Add respawn_delay to unit tests
Correct mock behavior

Needs to track time_of_death just like the real Process object