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>

 syntax: glob

 # Generated files

 configure

 autom4te.cache

 config.log

 config.status

 Makefile

 *ct-ng*

 docs/*ct-ng*.1

 docs/*ct-ng*.1.gz

 paths.mk

 scripts/crosstool-NG.sh

 scripts/saveSample.sh

 scripts/showTuple.sh

 kconfig/conf

 kconfig/?conf

 kconfig/**.o

 kconfig/**.dep

 config/configure.in

 config.gen/

 .config

 .config.2

 # Temporaries

 .*.swp

 build.log

 .config.old

 # This is the place where toolchains are built

 .build/

 # .. and the legacy location

 targets/