[Feature] Rename WorkflowExecutionIdentifier in flyteidl to ExecutionIdentifier

[katrogan]

Motivation: Why do you think this is important? Now that we're moving to a model where a standalone execution doesn't necessarily refer to a workflow execution (see https://github.com/lyft/flyte/issues/221) for clarity's sake we should update flyteidl. This change won't change any of the binary formats of flyteidl protobufs, but will require dependent repos to update their reference of the existing field name in code.

Goal: What should the final outcome look like, ideally? An execution shouldn't be called a WorkflowExecution in flyteidl.

Describe alternatives you've considered Leaving the name as is - and potentially confusing users in the future.

Flyte component

• [ ] Overall
• [ ] Flyte Setup and Installation scripts
• [ ] Flyte Documentation
• [ ] Flyte communication (slack/email etc)
• [ ] FlytePropeller
• [x] FlyteIDL (Flyte specification language)
• [ ] Flytekit (Python SDK)
• [ ] FlyteAdmin (Control Plane service)
• [ ] FlytePlugins
• [ ] DataCatalog
• [ ] FlyteStdlib (common libraries)
• [ ] FlyteConsole (UI)
• [ ] Other

[Optional] Propose: Link/Inline

Additional context

Is this a blocker for you to adopt Flyte

[kumare3]

Ohh this would be awesome, sad tech-debt

[github-actions[bot]]

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 engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏