More CI Updates

[bennibbelink]

After some discoveries made in cyclus #1667 some changes are necessary.

• build_test.yml doesnt push anything (including cache) to a package registry - this way a PR from a fork can perform testing with no issues

• publish_latest.yml is the ONLY workflow that updates the ci-layer-cache - this way any other workflow will be pulling layers from cymetric:latest

• some conversions of repository_owner to actor

• incorporated PR trigger for publish_release.yml from Add PR trigger for publish_release.yml #192.

• Any workflows that publish an image (i.e. publish_latest.yml and publish_release.yml) should be modified from a branch on the upstream. This is consistent with our old strategy

• changed default cycamore tag to latest from stable in the Dockerfile. This serves two purposes: to ensure users are using the latest version of cycamore, and to help make upstream workflows less verbose

[github-actions]

Build Status Report

Build FROM cycamore_20.04_apt/cycamore:latest - Success ✅
Build FROM cycamore_20.04_apt/cycamore:stable - Failure ❌
Build FROM cycamore_20.04_conda/cycamore:latest - Success ✅
Build FROM cycamore_20.04_conda/cycamore:stable - Failure ❌
Build FROM cycamore_22.04_apt/cycamore:latest - Success ✅
Build FROM cycamore_22.04_apt/cycamore:stable - Failure ❌
Build FROM cycamore_22.04_conda/cycamore:latest - Success ✅
Build FROM cycamore_22.04_conda/cycamore:stable - Failure ❌

[bennibbelink]

Expected failures of publish_release.yml since cycamore:stable doesnt exist yet

[gonuke]

A couple of Q based on consistency?

[gonuke]

Does it matter who we login as anymore?

[bennibbelink]

Not really since that workflow should be always be run from the cyclus repository. However, I think logging in as github.actor is more transparent as far as what permissions exist (and the example in the action docs uses github.actor)

[gonuke]

Thanks @bennibbelink - let's give this a shot...