Fix init permanence distance from connected threshold: TM, SP

[breznak]

TM initial and connected synaptic weights were mistakenly (by our changes in the past) initialized too far away. The intention was/is to init close to the edge of "connected".

• fixed in TM
• added init check to avoid this.
• SP should initialize closer to the middle (now 0.2 from 0.1, ideally move to 0.5 all)

This is a minor PR, ready to go as is. Changes doublechecked on NAB, no improvement/worse.

PS: As a follow up, I'd like to simplify the synapse init logic:

• drop Connection's argument connectedPermanence and hardcode this value (empirically no difference in 0.2, 0.5)
• in SP, TM drop related args for connected threshold and initial synapse.

[breznak]

There's a number of tests that are expected to fail and I'll have to update them. But the essence of the PR is here.

[dkeeney]

I see no obvious problems. I cannot judge on the algorithm.

[Zbysekz]

I also see no problem.

[Zbysekz]

PS: As a follow up, I'd like to simplify the synapse init logic:

drop Connection's argument connectedPermanence and hardcode this value (empirically no difference in 0.2, 0.5)
in SP, TM drop related args for connected threshold and initial synapse.

This would be nice, since it is simplification.