Fix debug CLI node recycling bugs
Fix debug CLI node recycling bugs

When creating a new - as opposed to recycled - debug CLI process node,
perform a proper barrier sync and node runtime update. Otherwise, the
graph replicas diverge for some period of time. That's not immediately
fatal, but it's not a good idea, either.

When renaming a debug cli process node, fix all of the name-vector
replicas before freeing the [one-and-only] name vector.

This fixes the so-called stats segment node runtime scraper crash,
which tripped over a replicated dangling reference to the
recently-freed debug CLI node name.

Change-Id: Ieffabd9f003139e534b9d79b88370439907930e5
Signed-off-by: Dave Barach <fb0929484eeb082cddd384774fcf105cc6ea7927@cisco.com>

chrisy/vpp,vpp-dev/vpp,chrisy/vpp,vpp-dev/vpp,FDio/vpp,chrisy/vpp,vpp-dev/vpp,vpp-dev/vpp,chrisy/vpp,FDio/vpp,chrisy/vpp,chrisy/vpp,vpp-dev/vpp,vpp-dev/vpp,FDio/vpp,FDio/vpp,FDio/vpp,chrisy/vpp,FDio/vpp,vpp-dev/vpp,FDio/vpp,FDio/vpp,chrisy/vpp