correctly setting execution environments in flyteidl

[hamersaw]

Tracking issue

NA

Why are the changes needed?

Execution environments require assignments to be passed at runtime.

What changes were proposed in this pull request?

Enable setting execution environments through flyteadmin protos.

How was this patch tested?

Locally.

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

#5311

Docs link

NA

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.19%. Comparing base (f59e5ae) to head (f3dcae3).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5323   +/-   ##
=======================================
  Coverage   60.19%   60.19%           
=======================================
  Files         646      646           
  Lines       45654    45654           
=======================================
  Hits        27481    27481           
  Misses      15581    15581           
  Partials     2592     2592           

Flag	Coverage Δ
unittests-datacatalog	69.31% <ø> (ø)
unittests-flyteadmin	58.78% <ø> (ø)
unittests-flytecopilot	17.79% <ø> (ø)
unittests-flyteidl	79.30% <ø> (ø)
unittests-flyteplugins	61.94% <ø> (ø)
unittests-flytepropeller	57.32% <ø> (ø)
unittests-flytestdlib	65.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.