[SYSTEMDS-3846] Perftest: Fix parfor forced CP compilation

The perftest runMSVM_10k_1k_dense_k5 reproducible failed on serializing
the parfor body program for a remote spark parfor job, because there
were remaining spark instructions (checkpoints). The reason was because
the forced CP compilation before such remote jobs was only applied in
a subset of cases and special hop properties were not correctly cleaned
up. This patch fixes the general issue.

Author: mboehm7

src/main/java/org/apache/sysds/hops/recompile/Recompiler.java

@@ -1509,8 +1509,12 @@ public static void rReplaceLiterals( Hop hop, LocalVariableMap vars, boolean sca
 	public static void rSetExecType( Hop hop, ExecType etype ) {
 		if( hop.isVisited() )
 			return;
-		//update function names
+		//update hop properties (exec type, spark lops)
 		hop.setForcedExecType(etype);
+		if(etype == ExecType.CP) {
+			hop.setRequiresCheckpoint(false);
+			hop.setRequiresReblock(false);
+		}
 		if( hop.getInput() != null )
 			for( Hop c : hop.getInput() )
 				rSetExecType(c, etype);

src/main/java/org/apache/sysds/runtime/controlprogram/ParForProgramBlock.java

@@ -834,8 +834,7 @@ private void executeRemoteSparkParFor(ExecutionContext ec, IntObject from, IntOb
 	{
 		// Step 0) check and compile to CP (if forced remote parfor)
 		boolean flagForced = false;
-		if( FORCE_CP_ON_REMOTE_SPARK && (_optMode == POptMode.NONE 
-			|| (_optMode == POptMode.CONSTRAINED && _execMode==PExecMode.REMOTE_SPARK)) ) {
+		if( FORCE_CP_ON_REMOTE_SPARK && _execMode==PExecMode.REMOTE_SPARK ) {
 			//tid = 0  because replaced in remote parworker
 			flagForced = checkSparkAndRecompileToCP(0);
 		}