#5661 [BUG] Eager workflows should not always use the latest pipeline version Issue created by ai-rnatour ### Describe the bug Currently, eager workflows always invoke the latest version of whatever task or workflow is being executed. This presents a number of problems: • When multiple developers are iterating on a pipeline in the

development

stage, their eager workflows might invoke tasks or workflows from other developers • Eager workflows prevent reproducibility guarantees for production pipelines For our use case, pipeline version pinning is important and this prevent us from taking full advantage of eager workflows. ### Expected behavior Eager workflows should accept a

version

field in their decorator to allow users to pin specific pipeline versions. If no

version

is provided, the eager workflow should default to invoking the same pipeline version as the currently executing task. This could be accomplished by examining the

FLYTE_INTERNAL_VERSION

environment variable. ### Additional context to reproduce No response ### Screenshots No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte