singleSelect not respected when selected === true on map config and/or multiple area config

[techfg]

Describe the bug
When singleSelect === true, IM should only allow a single area to be selected per the docs. However, when the map configuration has selected === true and/or multiple areas are defined with selected === true, IM does not enforce singleSelect behavior. Technically, this would be a misconfiguration but IM should likely enforce singleSelect regardless of selected configuration. This same issue occurs when rebind is called as well.

There is something to be said for permitting the misconfiguration and ignoring it (aka. treating it as intentional) and thus allowing multiple areas to be selected until an area is clicked by user and/or set/selected via API. Community feedback encouraged on how to handle this.

To Reproduce
Steps to reproduce the behavior:

1. Go to jsFiddle - selected is true in the map configuration
2. All areas are selected despite singleSelect === true
3. Go to jsFiddle - selected is true for configured areas paul & ringo
4. paul & ringo are both selected

Expected behavior
IM should enforce singleSelect and only select the first area it encounters that is selected === true

Screenshots
N/A

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
N/A

[techfg]

Per this test case, singleSelect should be ignored when applying selected state from configuration. This is working as expected so closing this issue.