k3s bosh release split

[poblin-orange]

to ease usage of k3s in bosh, and have clear alignment with upstream components, the k3s bosh release will be split in 4 bosh-releases

• 3 'packages" bosh releases, releases and versionned according to upstream components
  • https://github.com/orange-cloudfoundry/k3s-packages-boshrelease
  • https://github.com/orange-cloudfoundry/k9s-package-boshrelease
  • https://github.com/orange-cloudfoundry/nerdctl-package-boshrelease
• 1 wrapper bosh release, including only the wrapper mapping bosh lifecycle with k3s lifecycle
  • https://github.com/orange-cloudfoundry/k3s-wrapper-boshrelease/

The bosh manifest changes should be reduced, as we keep same jobs name in k3s-wrapper-bosh release.
the additionnal k3s-packages job from k3-packages bosh release should just be colocated with k3s-server and k3s-agent jobs

This new architecture, combined with Renovate and bosh release github action will enable continuous upstream artifact publication.
Bosh specifics will be versionned independenly in k3s-wrapper bosh release. The github issues, backlog and discussions will be moved in k3s-wrapper.