#2881 [Core feature] Flytekit execution models should expose more fields Issue created by katrogan ### Motivation: Why do you think this is important? Currently the execution models expose a subset of the underlying execution fields. We should expose the abort_metadata in the closure and reference execution in the metadata ### Goal: What should the final outcome look like, ideally? Flytekit Execution models should expose fields from the underlying protobuf definition from executions fetched using flytekit remote ### Describe alternatives you've considered Current implementation ### 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