Decrease code duplication in CI workflow-call action and yaml anchors

[CommanderStorm]

GitHub just shipped the feature to have yaml anchors:

• Support YAML Anchors actions/runner#1182

In the following issue we discussed at least one place where this might be benefitial:

• feat(new-dockerfile): add more metadata to the docker build #1877

There are likely a lot more of these places and the featre can remove lots of the duplicated code

[nyurik]

do we really want to use this?? I am not a big fan of "magic" - i.e. code that gets merged dynamically, e.g. combining multiple yaml lists together using anchors. Instead, I would much rather have dedicated custom github actions - that are reusable across different actions as needed. See https://github.com/maplibre/maplibre-rs/tree/main/.github/actions for examples

[CommanderStorm]

Both have a place imo

[nyurik]

i disagree - i think github actions should be as tiny as possible - because otherwise it becomes really hard to simulate them locally. Instead, I prefer most testing logic to be part of a justfile, including packaging and all other steps. Ideally, you should be able to run exactly the same everything locally, perhaps using docker + other stuff

[CommanderStorm]

For the strategy field of https://github.com/maplibre/maplibre-native-rs/pull/43/files anchors for example make sense

[nyurik]

sure, that one i would agree with, assuming we will always want to have the same list of test targets for regular and msrv. What i wouldn't want is for us to have a bunch of action steps shared between multiple workflows using yaml magic -- that should be done using proper "sub-actions"