Revert "[FilesBulkPinning] Ensure metadata changes invalidate all cached rows"

This reverts commit 78295daafd953f5fcce0cf6dfcde8641868f02f8.

Reason for revert: This has caused a regression on performance when
dropping a large number of files into Files app. Seems it
excessively redraws the list view causing it to hang.

Original change's description:
> [FilesBulkPinning] Ensure metadata changes invalidate all cached rows
>
> When metadata is retrieved the cache gets properly invalidated, however,
> only the items that are visible in the viewport get updated by the
> MetadataUpdateController. For items outside the viewport, these are
> cached in the FileListModel and when a user scrolls back the rows
> back into view, they can contain stale information.
>
> Currently many features appear to be invalidating their own individual
> metadata items (e.g. available offline toggle does the pinned icon,
> onDirectoryChanged does the modified time etc.). With the introduction
> of inline sync status this meant the status gets cached and not updated
> if out of view for long enough.
>
> This fix invalidates the indices that have new metadata changes and
> relies on the fact that the MetadataCacheSet only relays information for
> items which actually get changed (instead of blindly updating everything
> item even if nothing changes).
>
> Fixed: b:283204213
> Change-Id: If9e211a12465064b316a42799d1f973ce51e2bf8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4592153
> Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
> Commit-Queue: Ben Reich <benreich@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1154767}

Change-Id: Ia5c9c43e136c4a9a452b821f87ce6e5378d1ff38
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4635437
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Ben Reich <benreich@chromium.org>
Commit-Queue: Ben Reich <benreich@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1161019}