weston-init: Override the systemd service by a notify-based one

Using systemd notify, a service dependency would be more robust. This
allows, for example, another service to depend on weston-init without
having to hack a sleep (or similar).

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

meta-ohos-core/recipes-graphics/wayland/weston-init.bbappend

+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
 WESTON_DYNAMIC_INI ?= "0"
 WESTON_INI_PATH ?= "etc/xdg/weston/weston.ini"
 

meta-ohos-core/recipes-graphics/wayland/weston-init/weston@.service

+[Unit]
+Description=Weston Wayland Compositor
+RequiresMountsFor=/run
+Conflicts=plymouth-quit.service
+After=systemd-user-sessions.service plymouth-quit-wait.service
+
+[Service]
+Type=notify
+NotifyAccess=all
+User=%i
+PAMName=login
+EnvironmentFile=-/etc/default/weston
+StandardError=journal
+PermissionsStartOnly=true
+IgnoreSIGPIPE=no
+
+ExecStart=/usr/bin/weston-start -v -e -- $OPTARGS --modules=systemd-notify.so