Override 3 sec. WMI timeout in gopsutil

Add link to privacy policy in website footer

Add driver health information to node list stub

Added link to updated privacy policy in footer of `layout.erb` for the OSS website.

Fix the CPU Information error message

The default timeout is too short for some overburdened or resource
constrained machines to complete the WMI query before the context
deadline expires.  This causes them to be unable to fingerprint the CPU
properly.

The new version of gopsutil introduces a 3 second timeout that could come up as an error here; however, we are outputting the wrong variable and eating the error.

Cloud Auto Join

client/driver/env: interpolate empty optional meta params as empty strings

client/driver: remove unused const 'dockerPullProgressEmitInterval'

Fix deadlock in deadline timer logic when progress deadline is passed and the deployment is updated.

Fix the initial progress deadline calculation when the alloc is inplace updated to be part of a new deployment