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)

 # Build script for m4

 CT_M4_VERSION=1.4.13

 do_companion_tools_m4_get() {

     CT_GetFile "m4-${CT_M4_VERSION}" \

                {ftp,http}://ftp.gnu.org/gnu/m4

 }

 do_companion_tools_m4_extract() {

     CT_Extract "m4-${CT_M4_VERSION}"

     CT_Patch "m4" "${CT_M4_VERSION}"

 }

 do_companion_tools_m4_build() {

     CT_DoStep EXTRA "Installing m4"

     mkdir -p "${CT_BUILD_DIR}/build-m4"

     CT_Pushd "${CT_BUILD_DIR}/build-m4"

     CT_DoExecLog CFG \

     "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \

         --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"

     CT_DoExecLog ALL make

     CT_DoExecLog ALL make install

     CT_Popd

     CT_EndStep

 }