Save resolved execution time parameters in flyteadmin

[katrogan]

At create execution time, flyteadmin goes through a series of fallbacks to resolve runtime parameters in order of

1. The CreateExecution request spec itself
2. The launch plan spec
3. Workflow matchable attribute overrides
4. Project matchable attribute overrides
5. The root application defaults

Currently, we only save the CreateExecution request spec parameters in the db. We should save the final resolved value of the merged in workflow execution config in a separate blob in the db. It's useful to capture the request spec params themselves but it's hard to reason about what the actual runtime values are after the fact.

Ideally we save at what layer in all the override logic all the parameters themselves were sourced from for traceability and debuggability

[davidmirror-ops]

2023-11-09 Contributor's meetup notes: this entry is a better fit for an Issue, instead of an RFC. @katrogan feel free to create Issue from this discussion. Thanks!