Feat/232 invoice payment dispute evidence bundler

[adefemiesther1-debug]

Description
Closes #232
Overview
This PR adds a centralized forensic aggregation tool within src/disputeEvidenceBundler.ts to automate what was previously a manual, error-prone evidence collection process. By introducing a one-call asynchronous bundler, the SDK can now extract and unite cryptographic payment proofs, on-chain smart contract historical audit tracks, and raw network event records into a single, tamper-evident object format.

Changes
Branch Infrastructure: Created and isolated tracking workspace within feat/232-invoice-payment-dispute-evidence-bundler.

New Forensic Subsystem Added (src/disputeEvidenceBundler.ts):

Engineered bundleDisputeEvidence to concurrently retrieve and pack crypto proofs, get_audit_log storage entries, and indexing nodes' historical event vectors.

Integrated an automated integrity layer computing a top-level SHA-256 checksum across the structural data payload to block client-side modifications.

Public Boundary Mapping (src/index.ts):

Exposed the collection function and corresponding TypeScript types across the SDK's public index endpoint.

Integration and Integrity Testing Suite (src/tests/disputeEvidenceBundler.test.ts):

Added validation routines confirming full component structural presence, reliable checksum compilation, and instant corruption detection if internal variables are modified.

Operational Safety & Integrity Guarantees
Asynchronous Data Hydration: Utilizes non-blocking execution models (Promise.all) to query network endpoints concurrently, minimizing data-retrieval latency.

Tamper-Evident Audits: Incorporates deterministic key sorting during serialization to ensure checksum generation remains stable, accurate, and reproducible across varying runtime environments.

Verification & Testing Checklist
[x] Type Safety Verification: Confirmed full workspace configurations compile smoothly with zero TypeScript compilation faults.

[x] Linter Compliance: Cleared code styling checks via npm run lint to fulfill repository formatting criteria.

[x] Conventional Commit Integrity: Grouped file updates into an atomic conventional commit framework and pushed directly to origin.

[drips-wave]

@adefemiesther1-debug Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits