Enhance README: Shields to capture the attention of potential contributors

[devactivity-team]

I noticed you have opened issues labeled help wanted. I recommend enhancing the README to make the call for new contributors more prominent.

Changes Made:

1. Shields: Added Shields.io badges at the top of the README

[![GitHub repo Good Issues for newbies](https://img.shields.io/github/issues/kubernetes-sigs/ingress2gateway/good%20first%20issue?style=flat&logo=github&logoColor=green&label=Good%20First%20issues)](https://github.com/kubernetes-sigs/ingress2gateway/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) [![GitHub Help Wanted issues](https://img.shields.io/github/issues/kubernetes-sigs/ingress2gateway/help%20wanted?style=flat&logo=github&logoColor=b545d1&label=%22Help%20Wanted%22%20issues)](https://github.com/kubernetes-sigs/ingress2gateway/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) [![GitHub Help Wanted PRs](https://img.shields.io/github/issues-pr/kubernetes-sigs/ingress2gateway/help%20wanted?style=flat&logo=github&logoColor=b545d1&label=%22Help%20Wanted%22%20PRs)](https://github.com/kubernetes-sigs/ingress2gateway/pulls?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) [![GitHub repo Issues](https://img.shields.io/github/issues/kubernetes-sigs/ingress2gateway?style=flat&logo=github&logoColor=red&label=Issues)](https://github.com/kubernetes-sigs/ingress2gateway/issues?q=is%3Aopen)

2. Welcoming Message: Enhanced the README with a more prominent and inviting message to welcome new contributors.

Why This Matters:

• Attract New Contributors: Considering there is a number of opened issues labeled 'Help Wanted' - a welcoming and appealing README is one of the most efficient ways to attract new contributors

Additional Resources:

For more insights into building a strong open-source community, check out the Building Community guide.

🚀 Thank you for considering this pull request! 🚀

[linux-foundation-easycla]

• ❌ - login: @devactivity-team / name: Oleg . The commit (00749fd) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: devactivity-team
Once this PR has been reviewed and has the lgtm label, please assign youngnick for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[devactivity-team]

I also suggest enhancing the README with the following widgets using devActivity app:

1. Dynamic Top Contributors (with avatars linked to contributor profiles)

2. Repo Stats

Feel free to explore the Live Demo and Public Dashboard for a quick overview of the app.
It makes the contribution process more exciting with gamification elements like:

• 🌟 XP and Levels based on contributions
• 🏆 Challenges and Achievements
• 🏅 Leaderboard and much more!

Latest repositories using devActivity: barecheck (⭐55)

---

Simply install an app to bring a more comprehensive and engaging community experience.

🌟 Happy Coding! 🌟

[k8s-ci-robot]

Hi @devactivity-team. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[devactivity-team]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

That's the PR about. Anyway, closing it as old and unnecessary.
If anyone reads that, check devActivity app