ls-hubd*watchdogs are not working

:Release Notes:
Existing ls-hubd_p*_watchdog.conf jobs call reboot_ls-hubd_if.sh which
is missing in current versions.  The functions of that script have been
taken by crashd, so all the watchdog needs to do now is to leave a
cluse about who crashed and call reboot.

:Detailed Notes:
the two ls-hubd_private_watchdog.conf and ls-hubd_public_watchdog
have been combined into a single ls-hubd_watchdog.conf which simple
adds the name of the crashing program to the global environment
and then calls reboot.  The crash-logging functions formerly handled
by the init.d/reboot_ls-hubd_if.sh are now automatically handled
by crashd and rdxd.

:Testing Performed:
Other than a normal miniBAT, many kills of both ls-hubd_private and
ls-hubd_public using various signals. kill -INT causes the proc to
exit normally without causing a reboot (though you need to reboot
after that since the ls-hubs connections are built at boot-time),
kill -TRAP or kill -ABRT both reliably kill the hubs and cause
reboot - other signals likley will also, but I got tired of trying
them all.

:QA Notes:

:Issues Addressed:
[GF-45875] ls-hubd_p*_watchdog not working

Open-webOS-DCO-1.0-Signed-off-by: Ed Chejlava <ed.chejlava@lge.com>

Change-Id: I7ba5f4ebbf715ab9882b781d06b3d5c4291955f7
Reviewed-on: https://g2g.palm.com/3977
Reviewed-by: DCO Verification
Reviewed-by: Keith Derrick <keith.derrick@lge.com>
Tested-by: Keith Derrick <keith.derrick@lge.com>