Update from Chromium 84 to 87

Close for MM M3 release

Submitted the review request https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl-demo/+/27127 for chromium87 upgrade.

I am changing the plans. I am going to put on hold QtLess work, that is going to take some time, and work in a way that we can land chromium87 (and maybe next upgrade too) without applying the LG QtLess implementation. This is because most of the changes in upstream tree functionality came before they landed QtLess (so we can rebase on top of those). And after QtLess, at least right now, there are just very small changes.

Proceeding this way, we can update to 87 and next OSE release, fix functionality, and then once everything is ready, start preparing the new QtLess, independently of the current tree status.

P.S.: adapted the subtasks description accordingly.

P.S.: created https://lf-automotivelinux.atlassian.net/browse/SPEC-4239#icft=SPEC-4239 for new QtLess migration.

I am going to put this on hold. Right now master image with new application framework is starting to work, so I can already start with https://lf-automotivelinux.atlassian.net/browse/SPEC-4137#icft=SPEC-4137.

While we port to master, we give more time for a newer QtLess Chromium+Wam to come from webOS OSE, and we can cleanup our patch history to drop anything related to old framework. 

LGTM, you'll need a sane base to port upstream changes. Rebasing for AGL master (after koi) should be done afterwards. I've pretty much detailed the same thing in https://lf-automotivelinux.atlassian.net/browse/SPEC-4009#icft=SPEC-4009. 

Even if we don't really have full functionality for new appfw don't think it makes sense to further wait for that to get in/stabilize and until this and https://lf-automotivelinux.atlassian.net/browse/SPEC-4009#icft=SPEC-4009 is completed it might take quite some time.