Does it makes sense to lock global costmap when calling global planner?

[corot]

On old move_base both local and global costmaps are locked when calling the local/global costmap (see ros-planning/navigation#441).

On mbf only global costmap is locked. I think it should be done by the planner itself, just the minimum time possible.

[corot]

Solomonic decision: allow configuring the behavior.
Set local_planner_lock_costmap and global_planner_lock_costmap to true (the default) to lock the costmaps and so get the old move_base behavior.