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>

 # MIPS specific config options

 ## select ARCH_SUPPORTS_32

 ## select ARCH_SUPPORTS_64 if EXPERIMENTAL

 ## select ARCH_DEFAULT_32

 ## select ARCH_USE_MMU

 ## select ARCH_SUPPORTS_BOTH_ENDIAN

 ## select ARCH_DEFAULT_BE

 ## select ARCH_SUPPORTS_WITH_ARCH

 ## select ARCH_SUPPORTS_WITH_TUNE

 ## select ARCH_SUPPORTS_WITH_FLOAT

 ##

 ## help The MIPS architecture, as defined by:

 ## help     http://www.mips.com/