fix(artifacts): separate resolve artifacts for trigger of type pipeline

[nemesisOsorio]

Follow up to

• fix(artifacts): consider requiredArtifactIds in expected artifacts when trigger is pipeline type #4489
• fix(artifacts): Consider artifacts from stages when triggering from a pipeline stage #4568

Triggering a pipeline from Pipeline A using the pipeline stage where Pipeline B uses BakeManifestStage or DeployManifestStage which rely on expectedArtifacts is broken. ArtifactUtils is filtering the expectedArtifacts needed in stages.

In 1.28, you were able to define expectedArtifacts in Pipeline B, and when you triggered from Pipeline A, Pipeline B was able to resolve the artifacts from Pipeline A. Passing artifacts between pipelines

We are partially reverting some changes from:

• fix(artifacts): Be more lenient when filtering expected artifacts #4397
• fix(artifacts): consider requiredArtifactIds in expected artifacts when trigger is pipeline type #4489
• fix(artifacts): Resolving is broken in multiple places #4526

because they are not needed anymore.

Fixes spinnaker/spinnaker#6897

[nemesisOsorio]

Closing in favor of #4579