scripts/xldd: use user's sed and grep

xldd uses sed and grep as detected by ./configure. This works well if is
used on the machine that build the toolchain.

But if the user moves the toolchain to another machine where sed and grep
are not in the same directory (eg. /bin/sed vs. /usr/bin/sed), then xldd
will stop functionning.

Fix that by using ${SED} and ${GREP} if they are set in the environment.

Reported-by: Samuel Martin <s.martin49@gmail.com>
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