fix(plugin-import-export): incorrect user type in Export causing runtime type mismatch

[PatrikKozak]

What?

Separated user serialization concerns from runtime user handling in the export plugin by moving user and userCollection fields out of the base Export type into a new ExportJobInput type, and using a separate user parameter in CreateExportArgs.

Why?

The Export type had user: string which was meant for job queue serialization, but when exports ran directly (without job queue), the full user object was being passed where a string was expected. This created a type mismatch that only worked by accident at runtime.

How?

• Removed user and userCollection from base Export type
• Created ExportJobInput type that extends Export with serialization fields
• Updated CreateExportArgs to accept user?: TypedUser | null as separate parameter
• Fixed all call sites to pass user separately instead of in input object
• Added validation to ensure user exists before creating exports
• Job queue handler now strips serialization fields before passing to createExport

[github-actions]

📦 esbuild Bundle Analysis for payload

This analysis was generated by esbuild-bundle-analyzer. 🤖
This PR introduced no changes to the esbuild bundle! 🙌

Still reviewing

[github-actions]

🚀 This is included in version v3.66.0