merge meta-sdk-chrome additions back into meta-agl-demo (for rc1)

Closing as part of EE RC2

Pushing https://gerrit.automotivelinux.org/gerrit/11265:

ffmpeg-dev seems required to support Chromium video capabilities and it was added in the SDK by the previous patch.
But ffmpeg-dev is not available unless 'commercial' license is added to LICENSE_FLAGS_WHITELIST (this is the case for M3 because it's done in the BSP), but for other platforms, ffmpeg-dev is not available unless 'commercial' is added to the licenses white list.

So for EE.RC1, we have the following compromise:

• public releases will not contain ffmeg-dev and the provided SDK won't let developpers build Chromium with video support

• for Renesas Gen3 targets, there's nothing to do: the private built SDK will contain ffmpeg-dev

• for other platforms, 'commercial' should be added to LICENSE_FLAGS_WHITELIST to get ffmpeg-dev in the SDK and then be able to build Chromium.

The following topics should be investigated:

• can ffmpeg be substituted by another equivalent package, with open license ?

• does Chromium absolutely requires ffmpeg - can we build without ffmpeg ? what are the consequences ?

and : can you give your feedback here ?

@Walt: that topic may be also something to be discussed next week at AMM. Not only Chromium is impacted by the lack of ffmpeg. You can expect also some holes in gstreamer or any multimedia stack...

An alternative to add the target packages (the ones in TOOLCHAIN_TARGET_TASK) would be to include their counterpart in the image. So we can expect the -dev packages to be in the SDK.

For natives, I don't see other methods to get the tools like ninja or gn in the SDK.

OK let's keep that one open then.

This is good. Merging.

BUT we need to double-check what we declare in TOOLCHAIN_TARGET_TASK +=  is actually available in the agl-demo-platform. Thus we might have to do a follow-up and add a few things to the packagegroup "agl-demo" (or choose appropriate)