find-composition still depends on the composition property

["Juanma Barranquero" <lekktu@gmail.com>]

So, for example, C-u M-x describe-char does not describe composition
of characters now.


        character: ಸ (3256, #o6270, #xcb8)
preferred charset: mule-unicode-0100-24ff (Unicode characters of the
range U+0100..U+24FF.)
       code point: 0x3F38
           syntax: w 	which means: word
      buffer code: #xE0 #xB2 #xB8
        file code: ESC #x24 #x2C #x31 #x3F #x38 (encoded by coding
system iso-2022-7bit-dos)
          display: by this font (glyph code)
    uniscribe:-outline-Tunga-normal-normal-normal-*-13-*-*-*-p-*-iso10646-1
(#x63)


vs. the output before the change:


        character: ಸ (3256, #o6270, #xcb8)
preferred charset: mule-unicode-0100-24ff (Unicode characters of the
range U+0100..U+24FF.)
       code point: 0x3F38
           syntax: w 	which means: word
      buffer code: #xE0 #xB2 #xB8
        file code: ESC #x24 #x2C #x31 #x3F #x38 (encoded by coding
system iso-2022-7bit-dos)
          display: composed to form "ಸ್ಕಾ" (see below)

Composed with the following character(s) "್ಕಾ" using this font:
  uniscribe:-outline-Tunga-normal-normal-normal-*-13-*-*-*-p-*-iso10646-1
by these glyphs:
  [#<font-object
"-outline-Tunga-normal-normal-normal-*-13-*-*-*-p-*-iso10646-1"> 18 8
13 13 9]
  [0 3 3256 177 7 8 0 13 9 nil]
  [0 3 3256 101 8 8 0 13 9 nil]
  [0 3 3256 180 3 3 -2 13 9 nil]


 Juanma