What this PR does / why we need it:

Proposes adding Nikhil Kathole (@ntkathole) as a Feast project maintainer, recognizing his sustained contributions since June 2025.

Examples of his work include:

• Core capabilities: Ray compute engine and offline store (feat: Added Ray Compute Engine and Ray Offline Store Support #5526), complex types with schema validation (feat: Add complex type support (Map, JSON, Struct) with schema validation #5974), and first-class LabelView support (feat: Feast First-Class LabelView Implementation #6292).
• Lineage: OpenLineage integration (feat: Added support for OpenLineage integration #5884), cross-producer lineage consumption (feat: Add OpenLineage Consumer to Feast - receive, store, and visualize cross-producer lineage #6549), and expanded object coverage and visualization (feat: OpenLineage lineage enhancements - full object coverage, richer UI, and API-level sync #6719).
• Production deployment: Horizontal scaling in the operator (feat: Horizontal scaling support to the Feast operator #6000), feature server high availability (feat: Feature Server High-Availability on Kubernetes #6028), and ServiceMonitor generation for Prometheus discovery (feat: Add ServiceMonitor auto-generation for Prometheus discovery #6126).
• Performance and usability: DynamoDB latency improvements (feat: Optimize DynamoDB online store for improved latency #5889), HTTP connection pooling (feat: Add HTTP connection pooling for remote online store client #5895), and the REST API-backed UI for RBAC compatibility (feat: REST API-backed UI for RBAC compatibility and per-page lazy loading #6414).

Alongside these features, Nikhil has consistently contributed registry fixes, tests, CI improvements, dependency updates, and documentation. That combination of substantial development and ongoing maintenance demonstrates the ownership we want from maintainers.

Which issue(s) this PR fixes:

None.

Checks

• My commits are signed off (git commit -s)
• My PR title follows conventional commits format

Testing Strategy

• Testing is not required for this change

Documentation-only maintainer table update. Verified the diff with git diff --check and checked the contact against Nikhil's commit author information.

Misc

Per Feast governance, maintainer appointments require a private vote through the maintainer mailing list, open for at least seven days, with three maintainer +1 votes and no maintainer -1 votes. This PR prepares the roster update; merge after the required vote is confirmed.