[BUG] Flyteadmin not resolving execution spec fields

[katrogan]

Describe the bug

Execution spec fields like labels, annotations, security ctx and raw output data config can be set at different hierarchical layers starting with the create execution request, then the launch plan, then project level settings and finally global defaults.

Admin behavior incorrectly assumed that if you set any of those spec fields, we read all of them at the place where one was set and didn't do any fallbacks to read the other fields from descending hierarchical layers.

Expected behavior

Setting labels at create execution time shouldn't exclude reading the raw output data config from the launch plan (for example)

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[katrogan]

fixed by #2448