this issue is discussed as being "lowhanging UX fruits with few core effort",
once this is targeted a counterpart UI PR should be done

the current dc_forward_msgs takes a list of messages and a destination chat-id.

this issue is about enhancing/recreating the api to allow forwarding to a different profile.

the api would take:

• a source profile-ID
• a list of source message-IDs, if needed we can assume, they're all from the same chat
• a destination profile-ID
• a destination chat-ID

it seems fine if the new api is added to jsonrpc only.

not sure, how easy this is to do, iirc, we never had a cross-profile usage before.

if that gets too complex, we can think over alternatives, but for now, let's check if the above is doable