binutils: split binutils to backend/frontend, a-la cc_core

Move the actual binutils code to a backend function that builds the
required combo of build/host/target as requested by a frontend.

This split is currently a no-op, but is required for the upcoming
canadian-cross rework, where we'll be needing to build two binutils,
one for build/build/target, and one for build/host/target.

This applies to the three binutils:
- GNU binutils
- elf2flt
- sstrip

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

 # Overall toolchain configuration: paths, jobs, etc...

 # Allow unconditional usage of tristates

 config MODULES

     bool

     default y

 menu "Paths and misc options"

 source "config/global/ct-behave.in"

 source "config/global/paths.in"

 source "config/global/download.in"

 source "config/global/extract.in"

 source "config/global/build-behave.in"

 source "config/global/logging.in"

 endmenu