bugfix: cacheContext not passed to sudo

[0xAleksaOpacic]

Description

This PR ensures that we always work with a cachedContext when executing sudo logic. The store will only be updated if execution completes successfully (no error or panic). This prevents partial writes and ensures state consistency.

Why it matters

Without using a CacheContext, passing a plain ctx (sdk.UnwrapSDKContext(c)) means that any call to store.set or save inside a contract is written directly to the persistent MultiStore. This creates the risk of partial state commits:

BLOCKS.save(store, block.height, block)?;    // committed
// Out of gas happens here
NEXT_HEIGHT.save(store, &(block.height + 1))?;   // never reached

If an out-of-gas panic occurs after the first save, your defer may recover and return an error, but the earlier write has already been persisted. This leaves the chain in an inconsistent or unexpected state.

Solution

By wrapping the context with CacheContext, all writes are applied to a cached store. Only if execution completes without errors or panics do we commit the changes back to the main store. If an error or panic is encountered, the cached writes are discarded, ensuring atomicity of state changes.

[Copilot]

Pull Request Overview

This PR fixes a bug where state changes from sudo contract calls were persisted even when the call failed or panicked. The fix implements proper transaction atomicity by using a cache context that only commits changes on successful execution.

• Introduces cache context for atomic operations during sudo calls
• Ensures state changes are only committed on successful execution
• Prevents partial state modifications when contract execution fails

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}