minor-fix: lost-archiver refute logic

[tanuj-shardeum]

No description provided.

[linear]

BLUE-21 Bug when submitting the lost archiver refute request, causing a fatal error due to undefined properties in the update record function.

!channel, I found a way to take down active node, due to fake lost archiver message.
It worked for both release mode and debug mode but have to be an active node.

The request:

POST /lost-archiver-refute HTTP/1.1
Content-Type: application/json
Accept: **/**
Content-Length: 117
User-Agent: node-fetch/1.0 (+h
<ttps://github.com/bitinn/node-fetch>)
Accept-Encoding: gzip,deflate
Host: 127.0.0.1:9021
Connection: close

{"archiver":"testarchiver","cycle":"00000000000000000000000000000000","sign":{"owner":"justatest","sig":"justatest"}}

The node will procced the request if it is included the sign object with owner and sig.
In the new cycle, node will crash due to the archiver is not totally existed.
Here is the log message from node.

                                                                                                                                                                                                           [2024-02-05T10:46:18.150] [FATAL] fatal - unhandledRejection: TypeError: Cannot read properties of undefined (reading 'investigateMsg')                                                                                                        at Object.updateRecord (/home/shardeumcoredev/server/node_modules/shardus/src/p2p/LostArchivers/index.ts:126:47)                                                                                                                          at /home/shardeumcoredev/server/node_modules/shardu...

image.png

image.png