scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

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

 # This file declares functions for bare metal kernel (IE. none)

 # Copyright 2008 Yann E. MORIN

 # Licensed under the GPL v2. See COPYING in the root of this package

 CT_DoKernelTupleValues() {

     # For bare-metal, there is no kernel part in the tuple

     CT_TARGET_KERNEL=

 }

 do_kernel_get() {

     :

 }

 do_kernel_extract() {

     :

 }

 do_kernel_headers() {

     :

 }