Emit first node event after initialization on health status change

Check file contents when determining if agent should reload TLS confi…

Unmark drain when nodes hit their deadline and only batch/system left and add all job type integration test

only service allocs should have health watched

UI: Read the task event message from the DisplayMessage prop

Specify docker name in driver health messages

Allow to specify total memory on agent configuration

Refactor checksum comparison, always set checksum if it is empty

* Added extra debug logging; extended timeout; added jitter.

* small log changes

* increase timeout

* remove unneccessary uuid

drainer: reset index when new job registered

demo: give agents unique names

client: always mark exited sys/svc allocs as failed

drain: fix draining of system jobs

Create evals for system jobs when drain is unset

This PR creates evals for system jobs when:

* Drain is unset and mark eligible is true
* Eligibility is restored to the node

When restarts.attempts=0 was set in a jobspec a system or service alloc
that exited with 0 status would be marked as `completed` instead of
`failed`. Since system and service jobs are intended to run until
stopped or updated, they should always be marked as failed when they
exit even in cases where the exit code is 0.

Give demo agents unique names to improve `nomad node status` output.
Since the agents default to the hostname, they all had the same name
whether using the root or demo Vagrantfiles.