Add TGIN to Rust libraries section

[chesnokpeter]

Hi! I'd like to add TGIN to the Tools section.

It is an open-source load balancer written in Rust specifically for Telegram Bots. It solves the scalability issue for single-threaded bots (like aiogram/telegraf) by acting as a middleware buffer.

Key features:

• Handles 10,000+ RPS with 0% packet loss (verified benchmarks included in the repo).
• Works with both Webhook and LongPolling.
• Allows horizontal scaling (e.g., via Docker Compose) without changing the bot's source code.

I believe this will be very useful for the community, especially for high-load projects.

Link: https://github.com/chesnokpeter/tgin

[devloai]

PR Summary:

This PR adds TGIN, a Rust-based load balancer for Telegram bots, to the awesome-telegram list. TGIN is described as a high-performance infrastructure tool that handles 10k+ RPS and enables horizontal scaling for single-threaded bots. The tool acts as middleware between Telegram's API and bot instances.

Review Summary:

I've identified 2 issues that need to be addressed before this can be merged:

1. Critical - Wrong category: TGIN is currently added to "Bot Libs > Rust" but it's an infrastructure/load balancer tool, not a bot library. Per the repository guidelines on appropriate category placement, it should be moved to the Tools section (starting at line 192).

2. Medium - Formatting: The entry uses a hyphen (-) instead of the required em dash (–) separator, violating the repository's formatting standards per contributing.md.

The project link is accessible, serves a legitimate purpose in the Telegram ecosystem, and the description accurately represents the tool. Once the category placement and formatting are corrected, this will be a good addition to the list.

Knowledge utilized: Repository contribution guidelines (contributing.md), review instructions, formatting rules for awesome lists, and verification of TGIN's actual functionality via repository analysis.

Follow-up suggestions:

• @devloai move TGIN to the Tools section with correct formatting
• @devloai fix the identified issues