[Core feature] Flytekit execution models should expose more fields

[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?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[katrogan]

cc @wild-endeavor

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions[bot]]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏