Improve error messages and handle data structure anomalies

[Igor Shadurin]

We've encountered a situation where the data structure behaves incorrectly, but the error message provided by fdp-storage does not offer sufficient details to understand the issue. Specifically, we've found that if the first file of the pod is deleted, but the filename is not removed from the list of files of path /, the unencrypted version of chunkdata of the file is equal to __Fair__.

This ambiguous behavior makes it difficult to diagnose and resolve issues effectively. It would be beneficial to enhance the error messages to provide more detailed information when similar situations arise. This would help us understand the problem without needing to debug extensively.

In addition, we should handle this anomaly by displaying the list of files and directories without the problematic files. This would ensure the application continues to function as expected despite encountering such issues.

Finally, we need to identify the root cause of this situation and implement measures to prevent it from recurring.

The function where this issue occurs is src/content-items/utils.ts:31.

Acceptance Criteria:

• Enhance the error messages in fdp-storage to provide more detailed information about data structure anomalies.
• Implement a mechanism to handle such anomalies by displaying the list of files and directories without the problematic files (only for __Fair__).
• Investigate the root cause of the anomaly where the first file of the pod is deleted but its filename remains in the list of files of any path.
• Implement measures to prevent such anomalies from occurring in the future.