`@remotion/cli`: Incorrect error message for version mismatch between CLI and deployed lambda function

[UmungoBungo]

When rendering via lambda on the CLI, an incorrect message is shown when there is a version mismatch. In this example, there is a v4.0.286 function deployed, but the CLI is on v4.0.305.

pnpm exec remotion lambda render rive-animation webGlComposition --function-name=remotion-render-4-0-286-mem7167mb-disk10240mb-120sec --height=1280 --width=720

Function "remotion-render-4-0-286-mem7167mb-disk10240mb-120sec" does not match naming convention remotion-render-4-0-305-mem[memory]mb-disk[disk]mb-[timeout]sec.
Remotion relies on the naming to determine function information. This is an unsupported workflow.

The error message should instead be pointing out that the CLI is at a different version to the requested lambda function.

[bigboggy]

Same thing and there's absolutely no version mismatch anywhere

  err: Error: Version mismatch: When calling renderMediaOnLambda(), you called the function remotion-render-4-0-314-mem2048mb-disk2048mb-120sec which has the version 4.0.314 but the @remotion/lambda package is an older version. Deploy a new function and use it to call renderMediaOnLambda(). See: https://www.remotion.dev/docs/lambda/upgrading
      at Kwn (/var/task/index.js:152:19348)
      at gAn (/var/task/index.js:153:12525)
      at qAn (/var/task/index.js:153:25956)
      at async Runtime.handleOnceStreaming (file:///var/runtime/index.mjs:1206:26)
}```

[JonnyBurger]

@bigboggy Your problem is addressed in #5381

@UmungoBungo Your problem is addressed in #5382. Thanks for reporting!