Expand tracking of code optimizations - using ParserFast.allPattern

Add a test scenario looking closer at how `allPattern` declaration in the Elm syntax `ParserFast` library is emitted and executed at runtime.
Observed metrics in this version: Invocation count: 5. Instruction count: 175.
Looks like there are opportunities to optimize here.

Author: Viir

implement/Pine.IntegrationTests/CodeAnalysis/CodeAnalysisTestHelper.cs

@@ -5,10 +5,12 @@
 using Pine.Core.CodeAnalysis;
 using Pine.Core.DotNet;
 using Pine.Core.Internal;
+using Pine.Core.PineVM;
 using Pine.Core.PopularEncodings;
 using Pine.Elm;
 using System.Collections.Frozen;
 using System.Collections.Generic;
+using System.Collections.Immutable;
 using System.Linq;
 using System.Text;
 
@@ -154,4 +156,21 @@ public static (ElmInteractiveEnvironment.ParsedInteractiveEnvironment parsedEnv,
 
         return (parsedEnv, staticProgram);
     }
+
+
+    /// <summary>
+    /// Create a VM with all optimizations disabled, to support repeatable profiling.
+    /// </summary>
+    public static IPineVM PineVMForProfiling(
+        System.Action<PineVM.EvaluationReport> reportFunctionApplication)
+    {
+        var vm =
+            new PineVM.PineVM(
+                evalCache: null,
+                disablePrecompiled: true,
+                reportFunctionApplication: reportFunctionApplication,
+                precompiledLeaves: ImmutableDictionary<PineValue, System.Func<PineValue, PineValue?>>.Empty);
+
+        return vm;
+    }
 }