Serialised MinionTask do not represent the state properly and is being reported too often

[cielecki]

• Due to the previous usage of it, it does not reflect the state

• It should load verbatim, and set vars so it's not running anymore. Not the other way around where it's saved as not running.

• It's not clear from the analytics on what stage we are on, also which stage actually applied the modification

• No timing data, length of each stage, total length, startTime, endTime etc? Info if it's closed.

• data from minionTask is probably written to the db way to many times.