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>

 # s390 specific config options

 ## depends on EXPERIMENTAL

 ##

 ## select ARCH_SUPPORTS_32

 ## select ARCH_SUPPORTS_64

 ## select ARCH_DEFAULT_32

 ## select ARCH_USE_MMU

 ## select ARCH_SUPPORTS_WITH_FPU

 ##

 ## help Defined by IBM in:

 ## help     32-bit ESA/390       : http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar008/CCONTENTS

 ## help     64-bit z/Architecure : http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dz9zr002/CCONTENTS