Allow for changing number of syscalls

DTrace reports how many probes were matched.  Since the number of
syscalls can depend on the kernel, the number of matched syscalls
expected should not be hardcoded in our test result files.  This
problem seems to impact only test/unittest/syscall/tst.entry.d .

Add a .r.p post-processing file to mask out the exact number of
matched probes for this test.

Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>

test/unittest/syscall/tst.entry.r

@@ -2,4 +2,4 @@
                       mmap:entry 
 
 -- @@stderr --
-dtrace: script 'test/unittest/syscall/tst.entry.d' matched 333 probes
+dtrace: script 'test/unittest/syscall/tst.entry.d' matched NNN probes

test/unittest/syscall/tst.entry.r.p

@@ -0,0 +1,8 @@
+#!/usr/bin/gawk -f
+# Oracle Linux DTrace.
+# Copyright (c) 2020, Oracle and/or its affiliates. All rights reserved.
+# Licensed under the Universal Permissive License v 1.0 as shown at
+# http://oss.oracle.com/licenses/upl.
+
+/^dtrace: script .* matched [0-9]* probes/ { $(NF-1) = "NNN" }
+{print}