fix: don't fail if cache is corrupted

[sileht]

Related #7718

• Added tests for changed code.
• Updated documentation for changed code.

[sileht]

The goal is to show which cache key/path is corrupted to help to debug and get more information in future issues opened on this subject.

Tell me if the new behavior looks good, or if you prefer to keep the failure as before and convert the JSONDecodeError exception into a custom Exception that contains the key and the path of the problèmatic cache entry.

(I will add tests once we are ok with the solution).

[radoering]

IMO it makes sense to remove invalid entries. Maybe, the warning should say that the invalid entry is removed. If it only says that there is an invalid entry, but IIUC the entry is removed and will probably be replaced by a valid entry, an interested user, who opens the mentioned file, might be confused that the invalid entry seems to be valid.

[dimbleby]

duplicates #7453

[radoering]

Closing in favor of #7453

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.