Issue Summary:

orca's SQL pipelineRef feature doesn't populate the resolvedExpectedArtifacts field, causing error when using #triggerResolvedArtifact(String name).

Cloud Provider(s):

• GCP
• Kubernetes

Environment:

• Spinnaker 1.35.4
• Using pipeline trigger to propagate between clusters. Pipeline A deploy the Cluster A. Pipeline B has a trigger set to match successful run of pipeline B. Pipeline B match the docker artifacts of Pipeline A to decide which version to deploy.

Feature Area:

• Pipeline trigger

Steps to Reproduce:

• Spinnaker 1.35.4, with Orca config: executionRepository.sql.enabled=true and executionRepository.sql.pipelineRef.enabled=true
• Create two pipeline, pipelineA and pipelineB
• PipelineB has an automated trigger on pipelineA successful execution, with an artifact constraints
• PipelineB has an Evaluate Variables stage that use #triggerResolvedArtifact(String name) to use the expected artifact.
• Trigger pipelineA and see pipelineB triggering successfully but the resolvedExpectedArtifacts field is empty causing the Evaluate Variables stage to fail

Additional Details:

• pipelineRef

• Errors:

"expressionEvaluationSummary": {
                    "trigger['expectedArtifacts'][0]['boundArtifact']['version']": [
                        {
                            "description": "Failed to evaluate [COMMITID] EL1012E: Cannot index into a null value",
                            "exceptionType": "org.springframework.expression.spel.SpelEvaluationException",
                            "level": "ERROR",
                            "timestamp": 1731919796541
                        }
                    ]
                },

• Trigger setup: