These are options that can be configured for a launchplan during registration or overridden during an execution.
For instance two people may want to run the same workflow but have the offloaded data stored in two different
buckets. Or you may want labels or annotations to be different. This object is used when launching an execution
in a Flyte backend, and also when registering launch plans.
Optional location of offloaded data for things like S3, etc. remote prefix for storage location of the form s3://<bucket>/key... or gcs://... or file://.... If not specified will use the platform configured default. This is where the data for offloaded types is stored.