[Feature] Get*ExecutionData should optionally return data inline

[katrogan]

Motivation: Why do you think this is important?
The current model of fetching signed URL references to execution data [inputs + outputs] works fine in a hosted AWS environment but doesn't actually successfully return a usable link in local/sandbox mode. This is because "the url returned to flytekit is a presigned url, with the host name which is kubernetes cluster local - like - http://minio.flyte.svc.cluster.local:9000" (@kumare3) and makes for a frustrating and broken experience when standing up flyte locally.

Goal: What should the final outcome look like, ideally?
Ideally the Get*ExecutionData endpoints [Workflow, Node, Task] should allow callers to specify whether they want populated inputs & outputs in addition to signed URL blobs pointing to where the same data is stored.

The endpoints should remain separate from Get*Execution as is, but offer more customizability.

Describe alternatives you've considered
Oneof responses that include either the URL blob or the populated inputs. However URL blobs are cheap to generate and lightweight to pass around so we can keep them as is.

Optionally the inputs & outputs can be returned inline in the Get*Execution responses but this risks bloating them.

Flyte component

• Overall
• Flyte Setup and Installation scripts
• Flyte Documentation
• Flyte communication (slack/email etc)
• FlytePropeller
• FlyteIDL (Flyte specification language)
• Flytekit (Python SDK)
• FlyteAdmin (Control Plane service)
• FlytePlugins
• DataCatalog
• FlyteStdlib (common libraries)
• FlyteConsole (UI)
• Other

[Optional] Propose: Link/Inline

Additional context
First raised by @kumare3

Is this a blocker for you to adopt Flyte
N/A

[katrogan]

cc @kumare3 @wild-endeavor