Add WAL for direct deployment state recovery

[varundeepsaini]

Closes: #4090

Changes

Add write-ahead log (WAL) to record state changes during direct deployment, enabling recovery of partial state if deployment is interrupted.

Why

Today, if deployment is interrupted before Finalize(), no state is saved, and created resources become orphaned. The WAL writes each state change immediately to disk and replays them on restart.

Tests

Unit tests added for WAL save/replay, delete/replay, finalize cleanup, and edge cases.

[varundeepsaini]

@denik
Had a question, should the WAL be written to a new file, or should it be on the same file as the state ?
If a new file, then any write/read ops to the WAL that give an error, how should they be handled?

[github-actions]

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

• PR number: 4106
• Commit SHA: baf371eba4b51a7d13a95fdf8e6c8cbd1104e717

Checks will be approved automatically on success.