Remove duplications from test runner

[akosthekiss]

• Code contains syntactic duplications (e.g., build options copy-
  pasted repeatedly).
• Build options for test suites contain semantic duplications
  (ES5.1 profile builds happen multiple times, once by not
  specifying a profile and once by specifying es5.1 profile
  explicitly).
• External build options are not taken into account when detecting
  duplicated builds.

This patch provides improvement for these issues.

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss [email protected]

[akosthekiss]

Effect on Tracis CI:

job	on master	on PR
"Linux/x86-64 Build & Correctness Tests"	5:39	4:29
"Linux/x86 (cpointer-32bit) Build & Correctness Tests"	6:57	5:36
"Linux/ARM Build & Correctness Tests"	16:56	14:55
"OSX/x86-64 Build, Correctness & Unit Tests"	13:35	10:18
"ASAN Tests"	17:21	10:56
"UBSAN Tests"	10:07	6:18

(Execution times to be taken with a grin of salt as they can exhibit even +-2 mins of deviation.)

Example effect on executed test jobs: for UBSAN, the following equivalent test jobs are not executed multiple times superfluously:

• jerry_tests-es5.1-debug == jerry_tests-es5.1
• jerry_tests-es5.1-debug-snapshot == jerry_tests-es5.1-snapshot
• jerry_tests-es5.1-debug-cpointer_32bit == jerry_tests-es5.1 (!!!)
• jerry_test_suite-minimal-debug == jerry_test_suite-minimal
• jerry_test_suite-minimal-debug-snapshot == jerry_test_suite-minimal-snapshot
• jerry_test_suite-es2015_subset == jerry_tests-es2015_subset-debug
• jerry_test_suite-es2015_subset-debug-snapshot == jerry_test_suite-es2015_subset-snapshot

(The why: UBSAN has --debug as an external compile flag that makes debug and "non-debug" test jobs equivalent. It also has -m32 and --system-allocator=on, which makes the --cpointer-32bit=on --mem-heap=1024 flags of the jerry_tests-es5.1-debug-cpointer_32bit test job irrelevant.)

Note: This PR partially reverts #2217.

[LaszloLango]

AFAIK, the sanitizers only works with the system allocator. There is no make sense to run them with jerry allocator.

[akosthekiss]

@LaszloLango No question. But run-tests.py has a fixed set of test jobs to run (each has its own set of build options) and CI jobs can only append extra build arguments to them (the same set of extras to every test job). There is no way (at least now) to select which test jobs to run individually, e.g., from the list of JERRY_TESTS_OPTIONS. If --jerry-tests is given on the command line, all 7 jobs listed therein will be executed.

[zherczeg]

LGTM

[yichoi]

LGTM