chore(ci): Carry optional: true on needs for included jobs

Andrew Dunnrequested to merge
chore/needs-optional into main

What

The catalog container component creates container-build through a job_name input, so these needs: entries name a job this file does not define. Reference's pipeline standard requires such a need to carry optional: true.

Why

Landing this before reference_version: moves to v2.4.0 makes that bump a no-op, rather than turning the pipeline standard red here first.

Validation

Reference's own checker, just check-one STANDARD=pipeline REPO=<this tree>, with the needs-optional:.gitlab-ci.yml assertion clearing 3 to 0. The other five pipeline assertions still pass.

Merge request reports