does not allow performance optimization in logic

[Kevin222004]

This issue we have faced in loops where some conditions are for breaking the loop but Pitest will force to remove that logic
for example

        while (result
                && !isUsedVariableDeclarationFound
                && currentSiblingAst != null) {

mutated as

        while (!isUsedVariableDeclarationFound
                && currentSiblingAst != null) {

by the removal of the result, the output will not affect.
but the whole loop can run for more time than it was running with the result. This type of change is not good as it might lead to a problem. checkstyle/checkstyle#13120

similar issue faced at checkstyle/checkstyle#13557,
checkstyle/checkstyle#13149

[romani]

This type of change is not good as it might lead to a problem.

We did update to do extra loop only because this is nano optimization will not do any significant difference, but dealing with alive mutation cost more in long run.

But we give this feedback to share that some extra loop iteration might be costly and maybe there is a way to update mutation to not raise such cases as survivals.