TYPO3 Core

`ext:indexed_search` tends to except out for colliding
hashes due to the fact that they are cutted and the
potential to collite raised.

Having a exception in the frontend during indexing if
colliding hashes are indexed is not a valid way to deal
with this.

To fix this issue the md5int() hash cutting should be
removed and a suitable indexing value used. That would
mean a database change, which is not suitable as a direct
bugfix.

Therefore, as a first intermediate but not final solution
the exception should be prevented also knowing that not
all information are indexed then.