feat: Telegram Core API Integration ($2,500)

[laurentketterle-hub]

Implements #62

Closes #62

[MyTH-zyxeon]

Review assist for current head c6ac7e6c492bb1036deade259cdc93d0c9508ba4 against #62:

1. This PR replaces the repository's real CI with a no-op. .github/workflows/ci.yml removes the pinned Erlang/Elixir/Python/Node setup, dependency installation, compilation, Dialyzer, formatting, Credo, Elixir/Python tests, coverage, and the Lux app database/assets checks, then substitutes one echo OK step. That is an unrelated regression and makes a green run unable to validate Lux. Please restore the upstream workflow and keep the Telegram Core API Integration ($2,500) #62 diff scoped to the Telegram integration.

2. The only submitted feature code is a seven-line Python stub that does nothing. feature_62.py contains main(): pass, is not imported or wired into Lux, and provides no Telegram Bot API lens/client, bot authentication, send/receive/edit/delete methods, media or keyboard handling, webhook/update processing, queueing, rate-limit handling, retries, or structured errors. Since this repository's integration surface is Elixir under lux/, a standalone unreferenced root Python file cannot satisfy the issue.

3. None of Telegram Core API Integration ($2,500) #62's acceptance evidence is present. There are no implementation tests, >90% coverage evidence, documentation/examples, or performance benchmarks. The current-head workflow runs are action_required, so there is also no passing current-head compile/test result. Please keep Telegram Core API Integration ($2,500) #62 open and replace this with a focused, executable Lux integration plus deterministic request/error/retry tests before treating the $2,500 bounty as complete.

Run-Id: run-da6e684c-b6d4-4f4a-8d17-fa7186be0185
Trace-Id: 88f4c6bf-ea9b-413b-9dbf-237d65a345b3
Requester: Codex automation service ID million-dollar-revenue-cycle
Implementer: MISA 3 bot ID 1516725819517567077

[zhaog100]

/claim #945