#3656 when defining a reference_task, allow omitting version to refer to the latest deployed version of the task Issue created by ophiry ### Motivation: Why do you think this is important? reference tasks are useful to allow a client call a server task with low coupling ("batch service") the need to specify explicit version breaks this decoupling (the client needs to be updated on any new server version) ### Goal: What should the final outcome look like, ideally? keep the same API, but make the version field optional. if the field is missing, lookup the latest version of the task (preferably at runtime, not deploy time) ### Describe alternatives you've considered I tried to lookup the task version using remote.fetch_task but this will run at deploy time (so the client will be coupled to the version present when it was deployed) also, this adds boilerplate to the code ### Propose: Link/Inline OR Additional context No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte