CIAO: before_merging/scheduled, pt 3: build

Stack

• !12377 (merged): Generation check
• !12378 (merged): before_merging/scheduled -- scaffolding
• !12382 (merged): before_merging/scheduled -- sanity, packaging
• !12397 (merged): before_merging/scheduled -- build <- You are here
• !12490 (merged): before_merging/scheduled -- test (1)

What

Adds the CIAO translation of the build stage for the before_merging/scheduled pipelines, excluding debian_repository.yml.

Why

debian_repository.yml will be the subject of a future MR.

How

No big surprises here. Did some refactoring as well regarding variables for the Docker jobs.

Manually testing the MR

This MR is best reviewed commit-per-commit for the OCaml part. Commits should have a message explaining any non-obvious changes.

For the generated YML, do review the result of this command (see previous MRs like !11501 (merged) for setup instructions for gci-tezos):

$ gci-tezos diff-full-config master . schedule_extended_tests
$ gci-tezos diff-full-config master . before_merging
$ gci-tezos diff-full-config master . master_branch,test_release_tag,release_tag,non_release_tag,non_release_tag_test,beta_release_tag

The first command will show that this MR only strips irrelevant rules and trigger dependencies from the scheduled pipeline.

The second and third command shows no diff.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR