fix: remove crash residue

[zhourrr]

No description provided.

[greptile-apps]

Greptile Summary

Adds defensive cleanup logic to handle crash residue in two initialization methods: create_vector_indexer and init_memory_components. Before creating new index files or forward block files, the code now checks if these files already exist and removes them with a warning log. This prevents initialization failures caused by leftover files from previous crashes.

The implementation follows existing patterns in the codebase where file cleanup doesn't always check return values, relying instead on subsequent Open() calls to catch any issues. The changes are well-commented and use appropriate warning-level logging to track when cleanup occurs.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk as it adds defensive cleanup logic for crash recovery
• The changes are straightforward defensive additions that improve crash recovery. While the RemoveFile return values aren't checked, subsequent Open() calls have error handling that will catch any issues. The implementation follows existing patterns in the codebase and adds appropriate logging.
• No files require special attention

Important Files Changed

Filename	Overview
src/db/index/segment/segment.cc	Adds defensive checks to remove crash residue files before initialization; implementation is sound but could benefit from checking RemoveFile return values

_{Last reviewed commit: 4d3946a}