conformsTo generates validation errors even when used inside an "or"

[lmsurpre]

Describe the bug
for one of the PlanNet extensions we generate the following constraint:

value.as(Reference).exists() and 
value.as(Reference).resolve().conformsTo('http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-PractitionerRole') or 
value.as(Reference).resolve().conformsTo('http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-OrganizationAffiliation') or 
value.as(Reference).resolve().conformsTo('http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-Location') or 
value.as(Reference).resolve().conformsTo('http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-Organization')

For a reference of type Organization, we'll execute the conformsTo statements in order and we'll hit this on the first 3:

generateIssue(evaluationContext, IssueSeverity.ERROR, IssueType.INVALID, "Conformance check failed: profile (or base definition) '" + url + "' is not applicable to type: " + ModelSupport.getTypeName(modelClass), node.path());

To Reproduce
Run ExamplesValidationTest from #1441

Expected behavior
This should only generate an error if NONE of the or expressions are true.

Additional context
Similar, but different, from #1426