daemon components won't anymore embed *subdaemon.T

daemon components won't anymore embed *subdaemon.T

daemon components won't anymore embed *subdaemon.T

t.Stop() now returns when internal waitGroup is done

daemon components won't anymore embed *subdaemon.T

This commit also removes useless code: loop & httpHandler

daemon components won't anymore embed *subdaemon.T

DaemonApi has a new LabelNode member that is defined during api.RegisterHandlers
=> mocked hostname value during tests is applied to daemon api used label node

Previous implementation has unclear start/stop order.

Now created routines that has its own stop methods will use main t.ctx context:
- controller

other routines will use a cancelable context, that is cancelled during t.Stop()
- msgToTx
- msgFromRx
- janitor
- hb drivers

=> Stop()
   1- t.cancel() => cancel msgToTx, msgFromRx, janitor, hb drivers
   2- stop started hb drivers
   3- wait for wait group (msgToTx, msgFromRx and janitor are done)
   4- stop the controller

- msgToTx and msgFromRx returns when it detects cancellation while processing message

This stop the associated goroutine

## all components are now managed by the startStopper interface.

    - hbcache
    - ccfg
    - cstat
    - istat

## Stop function now waits for all components done before return.

## notifyWatchDog functions are now defined in dedicated functions:

    - notifyWatchDogSys (for systemd watch dog)
    - notifyWatchDogBus (for pubsub watch dog)

## use dedicated stopWatcher function to watch for daemon stop requests:

    - stop from signal
    - stop from msgbus.DaemonCtl

## update daemoncli to use Start from daemon instead of RunDaemon