decommission_controlm.sh and run_register_controlm.sh fail if active jobs use hostgroup/agent alias

[boogerburns]

decommission_controlm.sh and run_register_controlm.sh fail if active jobs use hostgroup/agent alias. The api will not let the agent alias be deleted if it is the same as the previous container's agent alias and there is active jobs ordered out against the hostgroup and/or agent alias. This causes both register and de-register scripts to fail and makes automating re-building a container with the same hostgroup and/or agent alias impossible. Manual intervention is required when this happens which defeats the entire purpose of this type of automation.