Move base VSS and KUKSA.val recipes to meta-agl-kuksa-val

Remove base VSS and KUKSA.val recipes, as they are moving to a new
meta-agl-kuksa-val layer in the meta-agl repository.  The recipes
for the Python modules they depend on have also been moved.

Additional changes:
- A new kuksa-can-provider-conf-agl recipe has been added to install
  our common AGL-specific kuksa-can-provider configuration.  The
  intent is that the kuksa-can-provider in meta-agl-kuksa-val not be
  dependent on our demo configuration choices.
- The other kuksa-can-provider configuration recipes have been
  tweaked to mark them as allarch.
- The python3-argparse-addons recipe and python3-cantools bbappend
  that used it have been removed, as it looks like it is no longer
  required.
- The dangling kuksa-val-agl-demo-cluster recipe has been removed,
  it was missed in the previous kuksa-val server removal.

Bug-AGL: SPEC-5136

Change-Id: I8c5aa556a796852c5ee3d8c26e045a089911f37e
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl-demo/+/30038
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
ci-image-build: Jenkins Job builder account
ci-image-boot-test: Jenkins Job builder account
Tested-by: Jenkins Job builder account

1 files changed, 1 insertions, 1 deletions

diff --git a/recipes-connectivity/kuksa-val/kuksa-can-provider-conf-gw-control-panel.bb b/recipes-connectivity/kuksa-val/kuksa-can-provider-conf-gw-control-panel.bb
index 02483a87..f2e9e673 100644
--- a/recipes-connectivity/kuksa-val/kuksa-can-provider-conf-gw-control-panel.bb
+++ b/recipes-connectivity/kuksa-val/kuksa-can-provider-conf-gw-control-panel.bb
@@ -22,4 +22,4 @@ RPROVIDES:${PN} = "kuksa-can-provider.env"
 ALTERNATIVE:${PN} = "kuksa-can-provider.env"
 ALTERNATIVE_TARGET_${PN} = "${sysconfdir}/default/kuksa-can-provider.gw-control-panel"
 
-RDEPENDS:${PN} += "kuksa-can-provider"
+RDEPENDS:${PN} += "kuksa-can-provider kuksa-can-provider-conf-agl"