[config] Warn againt using ash as CONFIG_SHELL

It apears that more and more ./configure scripts and Makefiles
make use of non-POSIXly correct shell constructs, that don't
work with ash.

For now, just warn the user against using ash, but keep it as
an option in case newer versions of the /broken/ components
come fixed, and we can again use ash, as it is in some cases
really faster than bash.

[config] Allow user to specify custom CONFIG_SHELL

In case the shell the user wants to use as CONFIG_SHELL is located in a
weird place (eg. /opt/bash/bin/bash), or is weirdly named (eg. bash-4),
let the user enter the patch to the shell.

[config] Add bash as a possible CONFIG_SHELL

On some systems and/or for some components, it may be necessary to
explicitly use bash as the shell used by ./configure and Makefiles.

[config] Change the way to select the CONFIG_SHELL

Transform the single boolean option to a 'choice' selection
with two options: "sh" and "ash".

This is needed to later add "bash" as override.

Merge the queue with all new component versions.

[cc-gcc] Add latest versions

Add gcc-4.4.1

[scripts-add-version] Handle gcc 4.4+

Handle gcc-4.4+ when adding a new gcc version.

[comp-lib-gmp] Add latest versions

Add 4.3.0 and 4.3.1.

[tools-libelf] Add latest version.

Add libelf 0.8.11, propagate patchset from 0.8.10.

[libc-eglibc] Add latest version

Add latest branch 2_10.