kconfig: install compiled frontends

The kconfig frontends are currently instaleld as source files. This is
a remnant of the early times, when I wanted a single installation of
crosstool-NG to be shared across multiple machines, potentially of
different architectures.

This does not really make sense, and it's been a long time since it
was las tpossible in practice.

So, just build the kconfig frontends at make-time, and install them
as we do for all other crosstool-NG dependent files.

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

 source "config/configure.in"

 source "config/backend.in"

 source "config/global.in"

 source "config/target.in"

 source "config/toolchain.in"

 source "config/kernel.in"

 source "config/binutils.in"

 source "config/cc.in"

 source "config/libc.in"

 source "config/debug.in"

 source "config/companion_libs.in"

 source "config/companion_tools.in"

 source "config/test_suite.in"