Figure out a strategy to prevent reads from live updates from causing production slowdowns

[dave-gantenbein]

[suprjinx]

perhaps an Aim UI story? Eg, an inactivity time-out which makes the user click "I'm still here" to resume

[suprjinx]

@jgiannuzzi suggested:

1. introduce a project-wide (ie, per namespace) setting to "allow live update"
2. when that setting is enabled, we show the live update control
3. when that setting is disabled, we remove live update control

[suprjinx]

i'm also thinking the autoloader could do something to compare the final received metric -- if there's no change in timestamp perhaps start an exponential backoff?

[suprjinx]

Solution for now: config switch when starting the server, send along to Aim in the projects endpoint, hide if disabled.