fix: randomSeed always ignored in ChatMistral node

[PythonToGo]

Problem

In ChatMistral.ts, the randomSeed variable was reading from the wrong input key:

// before (line 128)
const randomSeed = nodeData.inputs?.safeMode as string  // ← reads safeMode, not randomSeed

This means the Random Seed UI field is completely ignored — no value entered by the user is ever passed to the model.

Additionally, when safeMode is true, this bug causes randomSeed to receive "true" (a string), and parseFloat("true") evaluates to NaN, which is silently passed to obj.randomSeed.

Fix

// after
const randomSeed = nodeData.inputs?.randomSeed as string

Tested

• randomSeed set, safeMode off -> obj.randomSeed correctly assigned
• randomSeed empty, safeMode on -> obj.randomSeed not set
• randomSeed set, safeMode on -> both fields applied independently

[gemini-code-assist]

Code Review

This pull request fixes a bug in the ChatMistral component where the randomSeed variable was incorrectly assigned the value of safeMode instead of randomSeed. I have no additional feedback to provide.