Update main: Sui gRPC + JSON-RPC deprecation notice + Kite AI mainnet

[mikhailak]

Summary

Sync stage → main to publish:

• Sui gRPC docs — archive, testnet, GraphQL endpoints (feat: add Sui gRPC archive, testnet, and GraphQL endpoints #1936) + redirect format fix (fix: correct sui-grpc redirect format #1939)
• Sui JSON-RPC deprecation notice — per-service region info (docs(sui): JSON-RPC deprecation notice + per-service region info #1944)
• Kite AI mainnet — chain page + chains-list entry (docs(kite): add Kite AI mainnet chain page and chains-list entry #1945)
• Prior Update stage (#1935) carry

All component PRs are already reviewed and approved on stage.

Test plan

• Verify Kite AI page renders at /rpc-service/chains/chains-api/kite
• Verify chains-list includes Kite entry
• Verify Sui gRPC archive / testnet / GraphQL endpoint pages are accessible
• Verify Sui JSON-RPC deprecation notice shows on Sui pages
• Verify sui-grpc redirect format works

[mikhailak]

@baomastr — could you please dismiss your existing approval and re-approve to refresh the timestamp? 🙏

The PR has 1 approval, is mergeable, all signatures verify, and there are no failing checks. However the require_last_push_approval rule is blocking the merge button because GitHub's API returns pushedDate: null for the head commit de295ab0 — that commit landed on stage through the GitHub merge UI (#1947) rather than a direct push, and the rule can't validate "last push was approved" without a push event recorded. Known Rulesets quirk on merge-UI-created commits.

A fresh dismiss + re-approve refreshes the review state and should unblock. Alternatively any maintainer with admin merge can --admin past the block.

Once this lands, main will pick up: Sui gRPC archive/testnet/GraphQL (#1936), redirect format fix (#1939), JSON-RPC deprecation notice (#1944), Kite AI mainnet (#1945), plus the reconciliation merge (#1947).

Thanks!