Implement safeStringify for circular reference handling

[MK-2001]

Situation:
My flow aborted without information when the message was malformed with an editMessageText type.

Unhandled rejection TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Socket'
    |     property 'parser' -> object with constructor 'HTTPParser'
    --- property 'socket' closes the circle
    at JSON.stringify (<anonymous>)
    at TelegramOutNode.processError (/data/node_modules/node-red-contrib-telegrambot/telegrambot/nodes/out-node.js:86:128)
    at /data/node_modules/node-red-contrib-telegrambot/telegrambot/nodes/out-node.js:579:46
    at tryCatcher (/data/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/data/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/data/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/data/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/data/node_modules/bluebird/js/release/promise.js:725:18)
    at _drainQueueStep (/data/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/data/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/data/node_modules/bluebird/js/release/async.js:102:5)
    at Async.drainQueues (/data/node_modules/bluebird/js/release/async.js:15:14)
    at process.processImmediate (node:internal/timers:485:21)

Added a safeStringify method to handle circular references in JSON.

[windkh]

Hi, duplicated keys are removed. How is it even possible to have duplicated ones?
The object that is shown in the error does not contain all info. What if the removed key caused the problem?
Wouldnt it be better to return the raw message with a hint that the string is not a valid json?

[windkh]

Hi, duplicated keys are removed. How is it even possible to have duplicated ones? The object that is shown in the error does not contain all info. What if the removed key caused the problem? Wouldnt it be better to return the raw message with a hint that the string is not a valid json?

@MK-2001 what do you think?

[MK-2001]

It is not a directly a sublimated one, it mir a cut of a circulating structure in an object. If the same object gets identified twice, what is the origin of the current problem, it will crash the application.
Therefore I remove the second.

[windkh]

If so the root cause of the error should be pointed out clearly in the resulting object. Otherwise somebody will have problems when finding out what was going on.
Do you have a sample object for testing?

[windkh]

@MK-2001 Hi Marcus, I just did some investigation about how to handle this correctly
https://stackoverflow.com/questions/4816099/chrome-sendrequest-error-typeerror-converting-circular-structure-to-json

Instead of discarding the key somebody in the thread above replaced the reference with a string point out that this is a reference e.g. "circular reference"

What do you think about that?