Static update to the TAG Website landing page with contents from TAG README.md

[ragashreeshekar]

Per. CNCF service ticket https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-1988, TAG website template is a starting point and we maintain it henceforth. As discussed with the Chairs + TLs updating our website landing page with contents from our TAG README.md.

This is a static update to address #1116, however we might need to brainstorm approaches to ensure the README.md is mirrored in the website index for long term sustenance efforts.

[netlify]

✅ Deploy Preview for tag-security canceled.

Name	Link
🔨 Latest commit	d1fc521
🔍 Latest deploy log	https://app.netlify.com/sites/tag-security/deploys/65263113ea949a00079cbb7a

[anvega]

I noticed a few areas in the README that could benefit from updates:

• Workgroups Listing: The current list seems to not include all active workgroups. It would be beneficial for all teams if we could ensure every active workgroup is acknowledged in the README.

• Chairs Listing: This section also appears to be out of date. Let's make sure we reflect the current leadership accurately.

• Under the 'security reviews' section, my affiliation needs an update. I'd appreciate a quick revision there.

The considered mirror push strategy ensures content uniformity but introduces a delay between the README updates and the website content while the mirror push review happens at the destination. I think I would be beneficial to see that implementation first in the form of a chained pr before making this change in isolation risking the mirroring not happening a later time.

That said, given the website's information changes less frequently than the README, perhaps we could reconsider this approach. Would it make sense to directly adjust a few lines on the website repo occasionally for clarity and accuracy instead of relying solely on the mirror push?