v1 : MsDeploy under load can lead to host startup w/o functions

See ICM incident 192172973. Log analysis shows that a user initiated MsDeploy operation occurred, causing the normal host restarts as the host reacted to file change notifications. As the file system changed, the host recycled multiple times. Usually things stabilize and the final host instance restarts with a view of the newly deployed files. However, in this case, it looks like a race condition lead to the host running with no functions (there was supposed to be 1).

We need to review the file change / restart logic.

Start with ICM incident 192172973 and the host's file-change notification and restart logic. Reproduce or analyze the MsDeploy-under-load sequence, then verify that repeated host recycling cannot leave the final host instance running with no functions when one was deployed.

Written by the indexing model from the issue text.