Close fo Pike M1

We have a temporary fix from the compositor and two hot-fixes added.

Fyi with https://gerrit.automotivelinux.org/gerrit/c/src/agl-compositor/+/29012 in place this won't show up as an issue, as already noticed, but note that the shell client would take output dimensions into account while computing the activation area in the ini configuration file means it would only match a 1080p display resolution. A larger display would show other bits under.

Pushed an fix upstream and added as a patch in https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl-devel/+/29031 until upstream picks that up and does a meta-flutter update.

I sort of suspect this is related to multiple outputs, but I'll need to confirm first and I'll open a new jira ticket to handle that separately. We trip it over it just now, as we never relied on grabbing any output data (by that I mean the code in the embedder). As odd as this sounds, the embedder didn't made use of the output data until now. I think the code picks on the wrong output, rather than the where the embedder is at that moment, resulting in sending invalid data. We use ints in the protocol but uints in the code, hence negative values. This is a just a side-effect there's nothing particular to r-car3 other than ref-hw has two outputs, one of them being disconnected.

If that bump fixes the issue then I think we're fine until I submit a change ivi-homescreen side for Joel to pick-up it and do another meta-flutter update.