chromium: add use_system_libffi=true

As explained in:
2f5fe79
Chromium doesn't allow building with system libwayland anymore, and
needs (a static version of) libffi to build its own libwayland. Therefore,
libffi_%.bbappend was added to make libffi_pic.a (static library) available
while building chromium-ozone-wayland.

This libffi_%.bbappend is causing yocto-check-layer to give compliance error
for meta-chromium layer.

By adding "use_system_libffi=true" to GN_ARGS in chromium-ozone-wayland
recipe and removing the libffi_%.bbappend, we can make chromium-ozone-wayland
to build with libffi.so (shared library). With these changes, we can avoid
using libffi_pic.a (static library) for chromium-ozone-wayland build and
also resolve yocto-check-layer compliance error for meta-chromium layer.

Fixes: #714

Signed-off-by: Narpat Mali <narpat.mali@windriver.com>

Author: Narpat Mali

meta-chromium/recipes-browser/chromium/chromium-ozone-wayland_112.0.5615.165.bb

@@ -21,6 +21,7 @@ GN_ARGS += "\
         use_xkbcommon=true \
         use_system_minigbm=true \
         use_system_libdrm=true \
+        use_system_libffi=true \
         use_gtk=false \
 "