Randomize hourly update

[slominskir]

Currently the hourly update occurs 1 minute after the hour; but that means all instances of the app open around site (in each counting house) will issue a DB request at roughly the exact same time. If multiple instances are open per counting house we can run into a concurrent DB request limit (currently configured such that requests are queued for 5 seconds before timeout - and 3 are allowed concurrently). We could add a random number between 0 and 10 seconds for example to the refresh to spread the hourly refresh spike out. The current limits are fine for probably 10 concurrent users (due to queuing), but it appears users sometimes leave many more instances than that open in virtual desktops.