fix(weave_query): propgate tags on mapped run ops during gql key propagation

[domphan-wandb]

Description

Fixes WB-21889

Bug description

runs.loggedArtifactVersions causes a panel crash for users with the error:
No ops found for "tag-run" with first arg "TaggedValueType({['project', 'indexCheckpoint']}, artifactVersionType({'id': 'String()'}))"

The tag-run op expects an input type that's tagged with the run, but the tag is missing during compilation.

Solution

I added logic to handle propagating tags onto mapped run ops because the existing logic (should_tag_op_def_outputs) will only create a TaggedValueType if the opdef's input is a ProjectType or a singular RunType. In the case of mapped run ops, the inputs will always be a List of RunTypes. This specifically happens in run ops that are gql_connection_op.

Other mapped run ops have tags properly propagated because they go through the refinement codepath during compilation.

Testing

• I tested this through the UI in my dev environment

Screen.Recording.2025-01-13.at.7.57.01.AM.mov

• Previously, the runs.loggedArtifactVersions would cause a panel crash

[circle-job-mirror]

Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=bad8d9223968b2f65787da09758835bf4a65e99b