sdk: align cascade evidence payload with no-map chain schema

[mateeullahmalik]

Summary

Align supernode SDK cascade-client-failure evidence payload with chain proto no-map migration.

Changes

• Replaced map-based details payload with typed CascadeClientFailureDetails in SDK task pipeline
• Updated lumera adapter mapping into chain metadata struct
• Included storage-challenge evidence submission path as structured metadata flow via StorageChallengeFailureEvidenceMetadata (no map payload), plus dedicated helper/test coverage in storage challenge service
• Updated go.mod/go.sum to consume lumera commit with proto changes

Why

Keep SDK and chain metadata contracts in sync after map removal, and enforce explicit field-level payload semantics across both cascade-client-failure and storage-challenge evidence paths.

Validation

• go test ./sdk/...
• go test ./supernode/storage_challenge -run TestBuildStorageChallengeFailureEvidenceMetadata_NoMapPayload

[roomote-v0]

Rooviewer   See task

No issues found. The extraction of the struct literal into buildStorageChallengeFailureEvidenceMetadata is a clean mechanical refactor with correct field mappings. The new test validates both field correctness and the no-map serialization contract via JSON round-trip.

Previous reviews

• 2498dc6: Review #1

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}