Refactor FeasibleMinIIProperty

Just like issue #2 (closed), the FeasibleMinIIProperty is responsible for too many things right now. Some steps should be refactored/extracted/documented and tested properly (e.g. node placement, edge creation, ...).