scripts: fix dumping execution backtrace

Dumping the backtrace has been broken since changeset #652e56d6d35a:
scripts: execute each steps in a subshell

We can spawn sub-sub-shells in some cases.

The way the fault handler works is to dump the backtrace, but to avoid
printing it once for every sub-shell (which could get quite confusing),
it simply exits when it detects that it is being run in a sub-shell,
leaving to the top-level shell the work to dump the backtrace.

Because each step is executed in its own sub-shell, the variable arrays
that contain the step name, the source file and line number, are lost
when exiting the per-step sub-shell.

Hence, the backtrace is currently limited to printing only the top-level
main procedure of the shell.

Fix this thus:
- when dumping the bckatraces for the steps & the functions, remember
it was dumped, and only dump it if it was not already dumped
- at the top-level shell, print the hints

Also, rename the top-level step label.

Reported-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 4193d6e6a17430a177fa88c287879c2c35e319f3)

# Test suite config options

if EXPERIMENTAL

menu "Test suite"

config TEST_SUITE

    bool

config TEST_SUITE_GCC

    bool

    prompt "GCC test suite"

    depends on EXPERIMENTAL

    select TEST_SUITE

    help

      Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.

      The GCC test suite includes a collection of various toolchain tests for GCC -

      it utilizes the DejaGnu test framework.

      For some tests a network enabled target with ssh server is required.

      A helper Makefile is provided for running the tests - please see the included

      README for information on how to run the test suite.

endmenu

endif