[ENH] A tool for patching logs that were deleted before a new manifest was installed.

[rescrv]

Description of changes

PR #4972 fixed a bug wherein snapshots and fragments were deleted before
the manifest is installed. This has affected the dirty log on staging.

To fix it, we follow the prescription in the comments for this PR.

Test plan

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

N/A

[propel-code-bot]

Add Patch Tool/Helper for Logs Deleted Before Manifest Install

This PR introduces a new tool and supporting functionality for generating garbage collection patches in WAL3 when a bug causes logs to be deleted prior to manifest installation. The core change adds the function bug_patch_construct_garbage_from_manifest to reconstruct which files should be treated as garbage, and exposes this as a command-line utility for manual recovery. Regression tests are provided based on a 'real world' failure scenario.

Key Changes

• Added bug_patch_construct_garbage_from_manifest to Garbage in gc.rs to construct a patch set for deleted logs using a manifest.
• Introduced wal3-construct-garbage-from-manifest.rs as a CLI tool for operators to create garbage cleanup patches from manifests, fragment sequence numbers, and offsets.
• Added targeted test case covering manifest state encountered in production failures.

Affected Areas

• rust/wal3/src/gc.rs
• rust/wal3/src/bin/wal3-construct-garbage-from-manifest.rs

This summary was automatically generated by @propel-code-bot

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[Sicheng-Pan]

The garbage file needs to be manually uploaded to S3