Job Data exposes Authorization token

[LucidityDesign]

When passing the RequestContext to a new job, the authorization token will be stored with the job and exposed on the Job Queue page.
This enables admins to impersonate other admin accounts.

---

The documentation mentions how passing the RequestContext can be streamlines however it's difficult so understand which information is relevant for the specific use-cases.

Possible Solutions

1. Passing options to ctx.serialize() might help omitting unnecessary data. This could be an array of keys e.g. ctx.serialize(['channelToken', 'languageCode']) but there are probably better aproaches.
2. Update the documentation to make it easier to choose what context data should be passed into the job queue

[LucidityDesign]

Fixed in https://github.com/vendurehq/vendure/pull/5150/changes#diff-6f87ef28a57230a424dbbdd37ed3bdbd66ad5d49f3035b541e727179c5b35d97R35