Relax property identity-number checks in enum_is_in_range test.

We are now producing more checks, which was messing with the expectations
of the tests. Now made it a bit more general and all is good again.

Author: NlightNFotis

regression/cbmc/enum_is_in_range/enum_test5.desc

@@ -3,10 +3,10 @@ enum_test5.c
 --enum-range-check
 ^EXIT=10$
 ^SIGNAL=0$
-^\[main.enum-range-check.6\] line \d+ enum range check in ev3: SUCCESS$
-^\[main.enum-range-check.7\] line \d+ enum range check in ev2: FAILURE$
+^\[main.enum-range-check.\d\] line \d+ enum range check in ev3: SUCCESS$
+^\[main.enum-range-check.\d\] line \d+ enum range check in ev2: FAILURE$
 --
-^\[main.enum-range-check.6\] line \d+ enum range check in ev3: FAILURE$
+^\[main.enum-range-check.\d\] line \d+ enum range check in ev3: FAILURE$
 ^\*\*\*\* WARNING: no body for function __CPROVER_enum_is_in_range$
 --
 This test is for the enum_is_in_range working in assume statements