fix(replication): fix wrong memory status block replication

[mattisonchao]

Motivation

The follower didn't update the lastAppendedOffset status when the leader truncated the follower, which caused some expected entries to be filtered by deduplication logic and never recovered.

The server will keep printing:

{"level":"warn","time":"2024-11-13T11:38:33.0884113Z","component":"follower-cursor","error":{"error":"rpc error: code = Unknown desc = 20874694 can not immediately follow 20874678: oxia: invalid next offset in wal","kind":"*status.Error","stack":null},"follower":"xxxxxx","namespace":"xxxxxxxx","shard":13,"term":307,"time":"2024-11-13T11:38:33.088438126Z","message":"Error while receiving acks"}

Modification

• Align lastAppendedOffset alone with internal WAL headOffset.