Try disabling distance evaluation in `asiAlgo_ClassifyPointSolid` for the sake of better performance

In applications that require PMC but not distance evaluations (signed or unsigned), the logic implemented by asiAlgo_ClassifyPointSolid appears excessive because it not only checks for ray crossings but also evaluates the distance function. We assume that this distance evaluation adds significant computational cost and slows down the overall PMC test. In the scope of this ticket, we will investigate what happens to PMC performance when distance function evaluation is turned off. We will have to neglect the "ON" classification result, but this may not be critical.