Centralize File Closing with defer in ReplayCommand for Each Segment in WAL

[ayushsatyam146]

In the ReplayCommand function, within the loop that iterates through WAL segments, the file.Close() operation is called repetitively in multiple error paths whenever a problem is encountered during reading or unmarshaling an entry.
Relevant TODO

// TODO: We are reprtitively closing the file here
// A better solution would be to move this logic to a function
// and use defer to close the file.
// The function. thus, in a way processes (replays) one segment at a time.

One possible approach might be to:
Create a new private helper function (e.g., replaySegment(segmentPath string, cb func(*wire.Command) error) error) that is responsible for opening and fully replaying a single WAL segment file.
Within this helper function (or at the beginning of the for _, segment := range segments loop if a helper isn't introduced), place defer file.Close() immediately after successfully opening the file (os.Open). This ensures that the file is closed automatically when the function (or the loop iteration) returns, regardless of whether an error occurred.

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