Moved: New nodes should not get random activation if not allowed about carrot

[christianechevarria]

Removed in 6f2383b

Briefly added a check for mutation.MOD_ACTIVATION before mutating the new node but it didn't seem worth the performance cost

[christianechevarria]

@dan-ryan After some more testing, confirmed that this makes converging on a solution more difficult (which makes sense)

I'm thinking about reintroducing this but adding a flag to overwrite the default behavior.

Any thoughts?

[dan-ryan]

"but it didn't seem worth the performance cost"
One check hurt the performance that much?

Otherwise could just make it clear in the docs that there is this side effect.

[christianechevarria]

Restored it in f27e594

Just ended up adding a randomActivation property to the ADD_NODE object and a check to see if it's set to true (it is by default, but can be overwritten)

Closing for now