fix(log): handle large payload

[bodinsamuel]

Describe your changes

Fixes https://linear.app/nango/issue/NAN-1740/handle-large-log-payload-again

• Handle large log payload
  I had already fixed that but because we are now logging object + message in the sdk, the check has to be done twice.
  However, I also realized we have the same issue in the { input } object when triggering an action. (it can also happen inside our own codebase but less likely)

🧪 Tests

Failing validation

It should return a number, but returns a massive string

      returnTooLarge:
        description: trigger an returnTooLarge
        output: ReturnTooLarge
        endpoint: POST /unauth/act/returnTooLarge
      
    ReturnTooLarge:
      id: number

import type { NangoSync } from "../../models";

export default async function runAction(nango: NangoSync,): Promise<{ id: string }> {
  return {
    id: "a".repeat(10000000),   };
}

[linear]

NAN-1740 Handle large log payload (again)

[TBonnin]

should this file be called something like stringUtils.ts instead of json?

[bodinsamuel]

I asked myself the same question: it depends on how you interpret the name of the files: whether the input is important or the output.
This one takes a value as string but others takes Record, either they all related to json (no matter the encoding) or I move truncateJsonString in string.ts
Wdyt?

[TBonnin]

I don't feel strongly either side, json is not a bad name it is just a bit generic. Another option could be logFormatUtils.ts or something similar because those functions are mostly used in the context of logging. Feel free to keep it as it is though

[bodinsamuel]

I think we have many spots where json stringification could be an issue (that's why I moved it there actually); I'll leave it as is