Redesign widget pip and move into shared component

[toger5]

Fixes: #20383
Fixes: #32479

Related EC PR: element-hq/element-call#3775
copied from EC PR:

Screenshots / GIFs

Before	After

(The bottom after image is on hover)
Be aware that this is WIHTOUT the associated EW changes!
-> This just proves that things are not completely broken in case we fail on shipping them simultaneously.

With EW patches:

Before	After

Proving that things are not broken in case we fail on shipping them simultaneously.

• Add shared component for widgetPip
  • Using two different ways to pass subcomponents
    • for the avatar we just accept a react component that can be passed via a prop (this allow to give every component its own avatar)
    • for the PersistentWidget we pass the subcomponent via the viewmodel. The component is static. We basically just want to expose PersistenWidget type through the viewModel.
• remove pointer-events: none (we have the header now so it is acceptable to interact with the widget while in pip)
• remove hover logic for pip.
• adapt tests to use testid instead of deprecated mx_NAME class names
• checked that this works with jisti

WARNING:
We might want to block this PR on EC v0.18.0. We will loose the ability to hangup in pip mode with v0.17.0 and this PR merged (which is not the worst that could happen but also not idea.) (the workaround is: press the back button -> press the hangup button)

Checklist

• I have read through review guidelines and CONTRIBUTING.md.
• Tests written for new code (and old code if feasible).
• New or updated public/exported symbols have accurate TSDoc documentation.
• Linter and other CI checks pass.
• I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

[florianduros]

$width and $height is unknown in SC. Is it referring something in EW?

[toger5]

Yes we should remove that comment.

[toger5]

I think (to not block this on CI again) i will create a new PR with this comment cleanup + the renaming of the RoomHeaderBar file that was pointed out during the review.

[BillCarsonFr]

2026

[toger5]

I just decided to put this into this PR and not over to the other one I was mentioning here:

I think (to not block this on CI again) i will create a new PR with this comment cleanup + the renaming of the RoomHeaderBar file that was pointed out during the review.

[toger5]

So one more round of CI

[BillCarsonFr]

Thx 🙏, can't wait to test it.
just some minor comments on the headers

[BillCarsonFr]

should be 2025, 2026?

[toger5]

I think for this PR this is okay since its no diff to what it was before.

I will do the follow up PR. There we can update it if 2025, 2026 is the expected text.