test(frontend): add a --patch option to ML tests

[bcm-at-zama]

to test the removal of workarounds, or the use of new Concrete features

eg, ./ci/scripts/test_cml.sh --last_cp_version --patch patch.diff.txt

with the attached .diff.txt would check if the new VL works fine in ML.

closes #442

--

Remark that it tells you how are the files after modifying:

Installed Concrete-Python: concrete-python==2023.8.8
Applying patch /Users/benoitchevalliermames/Documents/Zama/Git/concrete/patch.diff
Modifications in ML repository:
diff --git a/src/concrete/ml/common/utils.py b/src/concrete/ml/common/utils.py
index 3af1800..5d1b3ee 100644
--- a/src/concrete/ml/common/utils.py
+++ b/src/concrete/ml/common/utils.py
@@ -40,7 +40,7 @@ MAX_BITWIDTH_BACKWARD_COMPATIBLE = 8
 # Use new VL with .simulate() by default once CP's multi-parameter/precision bug is fixed
 # TODO: https://github.com/zama-ai/concrete-ml-internal/issues/3856
 # Indicate if the old simulation method should be used when simulating FHE executions
-USE_OLD_VL = True
+USE_OLD_VL = False

patch.diff.txt

[bcm-at-zama]

Let me see the compliance pro

[bcm-at-zama]

Arg, bad merge from Git, I'll fix

[bcm-at-zama]

Rebased

[bcm-at-zama]

Should I merge it, @BourgerieQuentin ? Or maybe @youben11 wanted to comment on it?

[BourgerieQuentin]

close https://github.com/zama-ai/concrete-internal/issues/442