feat(drive-abci): debugging tool to replay abci requests

[lklimek]

Issue being fixed or feature implemented

When drive gives incorrect response to some ABCI request, we need a tool to reproduce the issue locally.

What was done?

Created new crate with two tools:

1. replay_abci_requests

• input: drive-abci database dir + ABCI RequestProcessProposal + .env with core config
• output: logs and apphash after processing the request

2. rocksdb dump - with some formatting to be more diff-friendly

How Has This Been Tested?

Locally

Breaking Changes

None, independent tool

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[github-actions]

✅ DashSDKFFI.xcframework built for this PR.

• Workflow run: https://github.com/dashpay/platform/actions/runs/19468208564
• Artifacts: DashSDKFFI.xcframework (folder), DashSDKFFI.xcframework.zip, xc_checksum.txt

SwiftPM (host the zip at a stable URL, then use):

.binaryTarget(
  name: "DashSDKFFI",
  url: "https://your.cdn.example/DashSDKFFI.xcframework.zip",
  checksum: "051c0e6e274f2828a2bc3f0dfb6950d20576b40b399e3d9df1db0590cb110510"
)

Xcode manual integration:

• Download 'DashSDKFFI.xcframework' artifact from the run link above.
• Drag it into your app target (Frameworks, Libraries & Embedded Content) and set Embed & Sign.
• If using the Swift wrapper package, point its binaryTarget to the xcframework location or add the package and place the xcframework at the expected path.