Implement phoenix2 conda package building per branch in CI

We want to be able to install a branch's code version as a package to test against other phoenix or SAG code. We also want to distinguish between branch's packages and release packages that should not be deleted and should be advertised to public.

• build packages with either names or preferably versions (more similar to container tags) that depend on the commit's branch (not commit ID, we only keep a single package per branch) and push those packages to phoenix-dev channel
  • Either the API allows to overwrite an exising package, otherwise need to delete an existing branch package first.
• in case of git tag: build a package with the git tag as version, and push to phoenix channel
  • git tag value may not match the CMakeLists project version, which is used to set the version in the recipe.yml. Investigate reading the project's version from git informations? (similar to python's setuptools_scm)
  • Also trigger gitlab release and include conda package as asset. See #20 (closed)

Examples: HiPeRTA CI variables and rules for building containers

FYI @paubert