multicast: dont cancel upstream sequence when client is cancelled

[twittemb]

Description

This PR makes the multicast operator iterate over the upstream sequence in a dedicated task so that collaborative cancellation does not apply. In a multicast world, the upstream sequence should continue to be iterated by new Tasks when one of its client is cancelled.

Checklist

• this PR is based on the main branch and is up-to-date, if not please rebase your branch on the top of main
• the commits inside this PR have explicit commit messages
• unit tests cover the new feature or the bug fix
• the CHANGELOG is up-to-date

[Kolos65]

Hey there @twittemb 🙋‍♂️

So then how do you cancel the upstream sequence or how will it be canceled? This leads to upstream sequences being stuck in the global scoped Task of the multicast sequence.

If you use share() for example to improve performance by not producing the same values of an expensive async sequence, the upstream sequence will never be cancelled properly after all clients are cancelled.

[Kolos65]

I think upstream sequences should be cancelled somehow if there are no clients and the only reference to them is the capture of the multicast sequence's Task.