Partially revert the scanning optimizations from 6dcda14
Partially revert the scanning optimizations from 6dcda14

Upon closer examination, there's no proof that this optimization
improved the performance. The function `entityNeedsUpdate` basically
always returned true because it compared also the `upated` timestamp
which was always different. Hence, it could only increase the time
used. But when it was modified to ignore the `updated` field, then no
measurable difference was seen. Probably any improvements seen earlier
were just random variance.

As the checking for `entityNeedsUpdate` doesn't provide any provable
benefit, it has no real reason or right to exist.

owncloud/music,paulijar/music,owncloud/music,paulijar/music,owncloud/music,owncloud/music,paulijar/music,paulijar/music,owncloud/music,paulijar/music