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>

 # Menu for the native GDB

 config GDB_NATIVE

     bool

     prompt "Native gdb"

     depends on ! BARE_METAL

     depends on ! BACKEND

     help

       Build and install a native gdb for the target, to run on the target.

 if GDB_NATIVE

 config GDB_NATIVE_STATIC

     bool

     prompt "Build a static native gdb"

     help

       In case you have trouble with dynamic loading of shared libraries,

       you will find that a static gdb comes in handy.

 endif # GDB_NATIVE