Add Robust Error Handling for `bufio.Writer.Write` in LogCommand in WAL forge

[ayushsatyam146]

The below TODO that can be found in the LogCommad method needs some analysis. The write operation to the buffered writer wl.csWriter.Write(bb) currently ignores potential errors by using the blank identifier. Evaluate whether any silent data corruption, loss, or an inconsistent state can occur and handle the errors gracefully.

// TODO: Check if we need to handle the error here,
// from my initial understanding, we should not be
// handling the error here because it would never happen.
// Have not tested this yet.

Setup Instructions

1. setup DiceDB server locally from the source - instructions
2. setup DiceDB Go SDK locally from the source - instructions
3. setup DiceDB CLI locally from the source - instructions
4. refer to the Pointing to local checked-out dicedb-gosection inREADME`.

Start the DiceDB server

$ go run main.go --log-level debug

Follow the contribution guidelines

These are general guidelines to follow before you submit a patch. Please mark them as done once you complete them

• please go through the CONTRIBUTING guide
• follow LOGGING best practices
• follow Golang best practices
• run make lint on your local copy of the codebase