Bugfix/not empty constructor creates bad bitmap

[AndrolGenhald]

Fix issue #87

DateStepTest->testMoscowWinterTime started failing when I was working on this, but it fails on master now too.

[Maks3w]

The proposed changes breaks current tests. Could you review it?

[Maks3w]

Please refactor this as a data provider.

[Maks3w]

The coverage drop is normal, less lines per file leads to a higher percent per (uncovered) line.

[Maks3w]

It's better create a new $options array here for to discard all those old values are now represented by $type.

[AndrolGenhald]

This would break options for AbstractValidator. I checked and it doesn't actually cause testTypeAutoDetectionHasNoSideEffect to fail, so maybe another test should be added that uses an array that has both types and AbstractValidator options? Either that or document that if the array has any non-type values it will just be treated as a normal options array.
It looks like the current constructor allows type strings to be combined with other options.

[Maks3w]

I appreciate the constructor needs more improvements. calculateTypeValue is called at least 3 times.

1. $this->setType($this->defaultType);
2. $this->calculateTypeValue($options));
3. parent::__construct($options); // if $options has the option key type

Could you take a look to this?

[AndrolGenhald]

calculateTypeValue should be called at most twice now, where the second call will only check 2 conditionals before returning. I don't think it's possible to guarantee that it'll only be called once, as there has to be some way to tell if the options array directly contains types.