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>

# Bare metal config options

## select BARE_METAL

##

## help 'Bare metal' refers to those programs that run without any kernel.

## help

## help You probably want to say 'y' here if you plan to use your compiler

## help to build bootloaders. It is not yet suitable to build Linux kernels,

## help though, because the APCI stuff relies on the target C library headers

## help being available?!?!...