Labday Github Action / Github Packages

[pacdaemon]

This work add a new pipeline into GitHub for building and publishing the output assets into Github Packages without resorting to our nexus repositories. This is a required for moving away from not only nexus but from Jenkins too.

See Github Packages

The required Github token for publishing the packages is passed by the Github Action to the runner as documented in this Github Document, it is not stored anywhere.
The proposed change in the development flow is, instead of connecting to the VPN for pulling the assets from the nexus repository, all the GitHub actions will pull them from GitHub. The security, who can read / publish packages depends on the writing/reading permissions to the repository allowing more granularity than the nexus repo (all people with access to the VPN).
The is an small change to be introduced on the local setup. People will need to define an environment variable (GITHUB_TOKEN) with a Github Personal Token instead. This approach is fully compatible with using the GH cli.
This will not be required until we deprecate the Jenkins builds.

After merging this PR:

• Jenkins pipeline -> publish to -> nexus repositories
• Github Action -> publish to -> GH Packages

Note, none of this work will affect builds on Jenkins, it is a non-disruptive work because of the approach I'm following.
This double build pipeline will allow me to cut PRs on dependent projects without breaking the pipelines.

Note: Slack notifications will be pulled from GitHub following the approach described on Slack

Work on this PR includes:

• Adding a github action
• Conditionally switch where it publishes based on a flag (GH action will set it)