hotfix: temporarily disable SDK/client complaint and storage challenge evidence submission

[mateeullahmalik]

Summary

Temporary incident-response mitigation to stop audit evidence submissions from supernode paths that can contribute risk during stabilization.

Changes

• Disable SDK cascade client complaint evidence submission:
  • sdk/adapters/lumera/adapter.go
  • SubmitCascadeClientFailureEvidence(...) now logs and returns without broadcasting tx.
• Disable storage challenge failure evidence submission:
  • supernode/storage_challenge/service.go
  • maybeSubmitEvidence(...) now logs and returns without broadcasting tx.

Validation

• go test ./sdk/adapters/lumera ./sdk/task ./supernode/storage_challenge

Notes

• This is intentional temporary mitigation per ops directive.
• Re-enable should be done in a follow-up PR once chain-side determinism hardening and validation are fully complete.

[roomote-v0]

Rooviewer   See task

Both previously flagged dead-code issues have been resolved by commenting out the if err != nil guards alongside the disabled SubmitEvidence calls. No new issues found.

• adapter.go:424-426 -- dead if err != nil block after commented-out SubmitEvidence call; err is always nil at that point
• service.go:619-621 -- same dead if err != nil pattern after commented-out SubmitEvidence call

Previous reviews

• 5e8f9ac: Review #1
• 59d8a49: Review #2

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