onboarding-progress-client for SWUpdate

This MR implements an example progress client to listen to progress messages from suricatta(wfx binding) during an onboarding update using wfx.

Why is this needed?

The onboarding update is treated as a configuration update and therefore would not need a bootloader state update. But the activation of the onboarding update would need a reboot or atleast restart of relevant services.

Setting the firmware tag in wfx jobs does reboot the system for activation (see Update Activation in SWUpdate docs) of the update but also updates the bootloader state which is undesirable for this case.

Hence the need for this simple module (essentially a trimmed down version of the upstream SWUpdate progress client) that currently just restarts the SWUpdate service during activation of the onboarding update.

How to include this in isar-cip-core images:

The necessary isar-cip-core recipes are available in a development branch. This installs the progress client in the target and set the necessary suricatta configs for wfx. Development branch: https://gitlab.com/cip-project/cip-core/isar-cip-core/-/tree/toshiba/wfx-integration?ref_type=heads

NOTE: Set WFX_URL variable in kas/opt/swupdate.yml

Build command:

./kas-container build kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/ebg-swu.yml:kas/opt/trixie.yml

@kshivanand @dinesh-toshiba @llbxg @zuka0828

Signed-off-by: Adithya Balakumar Adithya.Balakumar@toshiba-tsip.com