Identify the Failing ContractId using DiagnosticEventWalker

[codeZe-us]

In complex transactions with multiple cross-contract calls, it's difficult to know which specific contract caused a failure. Traversing diagnostic events allows us to pinpoint the culprit.

• Implement a DiagnosticEventWalker to traverse diagnostic events emitted during a failed transaction.
• Extract and surface the ContractId that triggered the final failure event.

Expectation: Prism highlights the specific failing contract ID in the UI, saving users from manually inspecting the diagnostic event logs.

Contributor telegram group: https://t.me/+sII7WPhll2liMGNk

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.