Add humans.txt

Community & Support: [LinkedIn Group](https://www.linkedin.com/groups/14656108/) · [Slack #project-nest](https://owasp.slack.com/archives/project-nest)

Active project leaders: Arkadii Yakovets -- [GitHub](https://github.com/arkid15r/) · [LinkedIn](https://www.linkedin.com/in/arkid15r/) · [Slack](https://owasp.slack.com/team/U060W3NKLTF); Kate Golovanova -- [GitHub](https://github.com/kasya/) · [LinkedIn](https://www.linkedin.com/in/kate-golovanova/) · [Slack](https://owasp.slack.com/team/U07PWB1JZ6Z)

[Contributing](https://github.com/owasp/nest/blob/main/CONTRIBUTING.md) · [Code of Conduct](https://github.com/owasp/nest/blob/main/CODE_OF_CONDUCT.md) · [GSoC Mentors](https://github.com/owasp/nest/blob/main/MENTORS.md)

---

**Describe the solution you'd like**

Summary

Add a humans.txt file to acknowledge the people who have contributed to the OWASP Nest codebase. The file should be generated dynamically using the same data sources as the /about page to ensure it stays up to date with minimal maintenance.

Motivation

humans.txt is a community convention for recognizing the people behind a website or project. While it is not an official web standard, it provides a simple, human-readable way to acknowledge contributors and maintainers. Since OWASP Nest already exposes contributor information through GraphQL endpoints used by the /about page, the same data can be reused to generate this file without introducing duplicate sources of truth.

Proposed Implementation

Implement a humans.txt that reuses the existing GraphQL endpoints powering the /about page.

The generated file should:

- List project leaders first.
- List all contributors who have contributed to the OWASP Nest codebase.
- Include names and optionally GitHub username
- Reuse the existing data sources rather than introducing new queries.
- Cache the generated response for 24 hours to avoid unnecessary API requests while keeping the content reasonably up to date.

**Are you going to work on implementing this?**

- [ ] Yes
- [x] No

**Additional context**
- https://github.com/actions/humans.txt

Start at the /about page and trace the existing GraphQL endpoints and contributor data sources; the issue does not name implementation files. Done means a dynamically generated humans.txt lists project leaders and contributors, reuses those sources, and caches its response for 24 hours.

Written by the indexing model from the issue text.