cc/gcc: do not use the core pass-2 to build the baremetal compiler

In case we build a baremetal compiler, use the standard passes:
- core_cc is used to build the C library;
- as such, it is meant to run on build, not host;
- the final compiler is meant to run on host;

As the current final compiler step can not build a baremetal compiler,
call the core backend from the final step.

NB: Currently, newlib is built during the start_files pass, so we have
to have a core compiler by then... Once we can build the baremetal
compiler from the final cc step, then we can move the newlib build to
the proper step, and then get rid of the core pass-1 static compiler...

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

 syntax: glob

 # Generated files

 configure

 autom4te.cache

 config.log

 config.status

 Makefile

 *ct-ng*

 docs/*ct-ng*.1

 docs/*ct-ng*.1.gz

 paths.mk

 paths.sh

 scripts/crosstool-NG.sh

 scripts/saveSample.sh

 scripts/showTuple.sh

 kconfig/conf

 kconfig/?conf

 kconfig/**.o

 kconfig/**.dep

 kconfig/lex.backup

 kconfig/lex.zconf.c

 kconfig/zconf.hash.c

 kconfig/zconf.tab.c

 config/configure.in

 config.gen/

 .config

 .config.2

 # Temporaries

 .*.swp

 build.log

 .config.old

 # This is the place where toolchains are built

 .build/

 # .. and the legacy location

 targets/