Remove os-refresh-config call from wipe-openstack.

Previously we were running os-refresh-config to make sure we
caught everything that had been refactored into orc scripts. After
analysis, it seems that the only thing we need before init-neutron is
init-neutron-ovs. This is called later in the orc chain, so we have
split wipe-openstack's call to init-neutron out into 85-init-neutron.

In addition, there was a check for "is it already running" behavior that
is no longer needed since we should only have one orc running at a time
with the impending lock change. We have removed that behavior.

Finally the init/wipe scripts don't need to be in the system PATH and thus
have been merged with their orc scripts, which were their only callers.

Change-Id: I407678104353b180102e16894408c3ffa2d7db90
Do not automatically start os-refresh-config.

cfn-hup needs to be the only thing running os-refresh-config. Otherwise
the other orc scripts will race with cfn-hup writing out new metadata.
The exception introduced here is to also let crond (which runs cfn-hup)
run os-refresh-config @reboot to seed the configuration.

Without a need to start up automatically, there doesn't seem to be any
good reason to use an upstart job / systemd service unit. Instead we
can just pipe os-refresh-config output to logger.

Also because we have several places to run os-refresh-config, we
need to move the locking into os-refresh-config itself. Please see
https://review.openstack.org/37319 for that change.

Change-Id: Ic35eca943ba76d421b61710b9fff018e17fb40bf
Merge "Remove os-refresh-config call from wipe-openstack."
Merge "Do not automatically start os-refresh-config."