cc/gcc: add the backend/frontend infra for final gcc

Currently, we issue the bare-metal compiler from the pass_1 & pass_2
core compilers, because the final gcc breaks while doing so.

This implies we have to build some libces during the start_files step,
instead of the standard libc step. This is the case for newlib.

By adding a backend/frontend infra to the final gcc, we can abstract
what backend to call: the standard backend for non-bare-metal gcc,
and the core backend for bare-metal.

This patch is just an no-op, it just adds the final backend and
frontend without changing the way bare-metal is built, to come in a
subsequent patch.

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

 # 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