status-page: fix race condition in initialization.

[turboMaCk]

Due to the fact that loading state text is inserted on window onload,
this insertion can potentially happen after all other async
actions are already finished and thus replace the actual data.
This fix makes sure that requests are triggered after onload is done.

cc @grahamc

This is what happens when the async actions are resolved with timing that leads to this issue:

Steps to reproduce:

1. make sure that client side cache is disabled in browser
   • common way is to set "disable caching while developer console is open" and open the console
2. refresh page several times until you hit critical timing in which issue occures.

[grahamc]

cc @samueldr mind taking a look-see?

[turboMaCk]

I've removed this wildcard _ for the argument name because in JS all arguments are optional (with default to undefined) and arrity of functions is pretty much dynamic. While I personally also like this convention of denotating ignored arguments with _ the problem in JS case is that one can never trust the number of arguments so it can be missleading when someone less experienced is reading the code and making assumptions about arity based on those wildcards even though in this case the arity won't change (unless some monkeypatching gets involved).

to make matters worse there are polupar libraries like lodash and underscore that make use of _ as a namespace for functions so using _ as an argument name can cause some unfortunete hard to track shadowing of those namespaces.

Not a big deal but better safe than sorry I would say.

[turboMaCk]

indentation of init changed to 2 space to be consistent with rest of the code. This is ready for merge from my side.