#3607 [Housekeeping] Refactor Flyte Literal handling to single location Issue created by hamersaw Describe the issue Currently, flytepropeller contains functionality to define literal type identification and casting (among other). Similar logic is spread between other repositories, including flyteidl. The goal is to consolidate this logic into a single location which can be imported from any flyte repo for use. The current situation specifically blocks type-checking partial arguments in maptasks because this requires the casting logic in flytepropeller withing flyteplugins - introducing a circular dependency. What if we do not do this? Logic may be unavailable, and therefore unnecessarily duplicated, between repositories. Related component(s) No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte