[BUG] [flytekit] Local execution of launch plan can be incorrect in some cases

[kumare3]

Describe the bug

LaunchPlan's can contain - fixed_inputs and default_inputs.
Fixed inputs are not overridable.

But the way launchplans are handled in flytekit local execution today, users can accidentally override fixed inputs. this should fail in the backend compiler, but will not be caught in local execution

this code sample shows how the saved inputs is a combination of the two and
it can be seen here how this will not be dealt with correctly in local execution and even in workflow creation.

Expected behavior

Failure in local execution if a fixed input is overriden

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

[kumare3]

Check out flyteorg/flytekit#1420, which fixes a similar issue for remote objects.

[github-actions]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏