feat(ci): trigger eicweb container build for benchmarks

[wdconinc]

Briefly, what does this PR introduce?

After some initial succesful running of eicrecon, we pass on to building a full eicweb container and subsequent benchmarks.

What kind of change does this PR introduce?

• Bug fix (issue #__)
• New feature (issue #__)
• Documentation update
• Other: __

Please check if this PR fulfills the following:

• Tests for the changes have been added
• Documentation has been added / updated
• Changes have been communicated to collaborators @sly2j

Does this PR introduce breaking changes? What changes might users need to make to their code?

No.

Does this PR change default behavior?

No. Won't make this test required (for now) so shouldn't slow down the pipelines until completion.

[wdconinc]

Well, that worked better than I thought it was going to: container build triggered, but with standard eicrecon.

[wdconinc]

Triggered correctly at https://eicweb.phy.anl.gov/containers/eic_container/-/jobs/2018552#L278

[wdconinc]

• Requires https://eicweb.phy.anl.gov/containers/eic_container/-/merge_requests/735

[wdconinc]

Seems to be working: eic_container triggered, which triggered detector benchmarks, which triggered both reconstruction and physics benchmarks. All are running so no final success or failure yet.

[wdconinc]

@veprbl This now works, and the last CI run through was successful through running the pipelines after building the temporary container, with the exception that it pushed that temporary container to a docker hub eicweb/jug_xl:eicrecon--default where there should have been a hash between the two dashes... i.e. https://hub.docker.com/layers/eicweb/jug_dev/eicrecon--default/images/sha256-7446018a5c52b4b1982ced5ec437eb240862988334a59037f257c45a7e7051ce?context=explore

[wdconinc]

This now works and should be ready for review and merging.

[veprbl]

Looks great!

[veprbl]

I'm wondering, if we'd need to propagate GitHub PR info from container pipelines to downstream pipelines somehow.

[wdconinc]

That used to be the case and it used to work. But changes in the way the benchmarks were reconfigured (https://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/merge_requests/150) introduced circular dependencies that broke propagation (https://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/merge_requests/154, https://eicweb.phy.anl.gov/containers/eic_container/-/merge_requests/736). So temporarily we don't have direct status callbacks from downstream benchmarks and only get the container status callback after the benchmark pipelines complete. I think that is probably ok for now.