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>

 # Super-H specific configuration file

 choice

     bool

     prompt "Variant"

 config ARCH_SH_SH3

     bool

     prompt "sh3"

 config ARCH_SH_SH4

     bool

     prompt "sh4"

 config ARCH_SH_SH4A

     bool

     prompt "sh4a"

 endchoice

 config ARCH_SH_VARIANT

     string

     default "sh3"   if ARCH_SH_SH3

     default "sh4"   if ARCH_SH_SH4

     default "sh4a"  if ARCH_SH_SH4A