[Core feature] Project labels doesn't reflect on kubernetes namespace

[yindia]

Motivation: Why do you think this is important?

Currently if we create/update any project with labels then those labels only stay in flyte ecosystem, But it would be great if we can pass those labels in k8s namespaces.

It's help full for management of different project in single cluster

Goal: What should the final outcome look like, ideally?

• Create project with labels
• Project labels should reflect on Kubernetes namespace

Describe alternatives you've considered

NA

Propose: Link/Inline OR Additional context

No response

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

• Yes

Have you read the Code of Conduct?

• Yes

[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! 🙏

[github-actions]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[kumare3]

labels are passed to executions as projects and namespaces do not have a 1:1 mapping. there are many orgs that run fewer namespaces than projects.