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>

# Options specific to crosstool-NG acting as a backend

config IS_A_BACKEND

    string

    option env="CT_IS_A_BACKEND"

config BACKEND

    bool

    default y if IS_A_BACKEND = "y" || IS_A_BACKEND = "Y"

config BACKEND_ARCH

    string

    option env="CT_BACKEND_ARCH"

config BACKEND_KERNEL

    string

    option env="CT_BACKEND_KERNEL"

config BACKEND_LIBC

    string

    option env="CT_BACKEND_LIBC"