call all effects on the actions queue

[Atrue]

Depends on #3
See only the latest commit.

The current behaviour:
The first effect is called immediately after the initialization of the component/model, so it may have unexpected results, like this:

Error: Assertion Failed: You attempted to update someProp on someModel, but it had already been used previously in the same computation. Attempting to update a value after using it in a computation can cause logical errors, infinite revalidation bugs, and performance issues, and is not supported.

Expected behaviour:
The first effect should be also called in the actions queue, to be safe to update any tracked properties there.

[BryanCrotaz]

implemented in 19428a6

Thanks for the idea!

EDIT:

On further checking, was already running all effects in the actions queue