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>

 CT_EXPERIMENTAL=y

 CT_LOCAL_TARBALLS_DIR="${HOME}/src"

 CT_SAVE_TARBALLS=y

 CT_LOG_EXTRA=y

 CT_ARCH_mips=y

 CT_TARGET_VENDOR="malta"

 CT_KERNEL_linux=y

 CT_KERNEL_V_2_6_38_8=y

 CT_BINUTILS_V_2_21_1a=y

 CT_CC_V_4_4_6=y

 # CT_CC_GCC_USE_GRAPHITE is not set

 CT_LIBC_EGLIBC_V_2_13=y

 CT_DEBUG_gdb=y

 # CT_GDB_GDBSERVER_STATIC is not set

 CT_GDB_V_7_2a=y

 CT_GMP_V_5_0_1=y

 CT_MPFR_V_3_0_0=y

 CT_TEST_SUITE_GCC=y