5.10.21 -- Fix issues with init fns firing order

- After the page has been initialized and the first batch of init fns
  have been run, calls to add-initfn! (or the with-init! macro) are
  fired immediately. This commit fires them from within a setTimeout
  because the assumption with init fns is that they fire "later".
  Consider for example a function that adds an init fn and returns some
  dom node. The assumption is that the init fn will be fired after the
  node is in the dom, which wouldn't happen without the timeout.
Merge branch 'master' of gh:tailrecursion/hoplon