CIAO: before_merging/scheduled, pt 2: sanity, packaging

Stack

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

What

Adds the CIAO translation of sanity and opam tests for the before_merging/scheduled pipelines.

Why

How

Sanity / hadolint jobs are pretty trivial. The opam jobs were translated by having manifest print the list of packages to test to a file in script-inputs and generate jobs based on that list.

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 arvid@ciao--mr-schedule--scaffolding . schedule_extended_tests
$ gci-tezos diff-full-config arvid@ciao--mr-schedule--scaffolding . before_merging
$ gci-tezos diff-full-config arvid@ciao--mr-schedule--scaffolding . test_release_tag,release_tag,non_release_tag,non_release_tag_test,beta_release_tag

The first two commands will show that this MR only does introduces some non-semantic changes in the opam package jobs (quotes around variable values, 1 minutes -> 1 minutes, adding default when: on_success).

The third command shows that nothing changes in release_tag pipelines.

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