doc: add description for global telegram_bot_token in document

[nutmos]

Pull Request Checklist

Please check all the applicable boxes.

• Please list all open issue(s) discussed with maintainers related to this change
  • Fixes #
• Is this a new Receiver integration?
  • I have already tried to use the Webhook Receiver Integration and 3rd party integrations before adding this new Receiver Integration
• Is this a bugfix?
  • I have added tests that can reproduce the bug which pass with this bugfix applied
• Is this a new feature?
  • I have added tests that test the new feature's functionality
• Does this change affect performance?
  • I have provided benchmarks comparison that shows performance is improved or is not degraded
    • You can use benchstat to compare benchmarks
  • I have added new benchmarks if required or requested by maintainers
• Is this a breaking change?
  • My changes do not break the existing cluster messages
  • My changes do not break the existing api
• I have added/updated the required documentation
• I have signed-off my commits
• I will follow best practices for contributing to this project

Which user-facing changes does this PR introduce?

add description for global telegram_bot_token in document

Summary by CodeRabbit

• Documentation
  • Enhanced configuration documentation with clarifying comments explaining the mutually exclusive relationship between two Telegram authentication configuration options, ensuring users understand they cannot be used simultaneously.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 560fd98f-a4ad-40b3-b2a8-0788f56650e3

📥 Commits

Reviewing files that changed from the base of the PR and between 8a11f85 and fc0f88b.

📒 Files selected for processing (1)

• docs/configuration.md

---

📝 Walkthrough

Walkthrough

Two clarifying comment lines were added to docs/configuration.md in the global Telegram settings section to document that telegram_bot_token and telegram_bot_token_file are mutually exclusive configuration options.

Changes

Cohort / File(s)	Summary
Documentation docs/configuration.md	Added two clarifying comment lines in the global Telegram settings section explaining that telegram_bot_token and telegram_bot_token_file are mutually exclusive options.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Two tokens, but never at once,
The docs now whisper their dance,
Mutual exclusion, clear as can be,
Configuration clarity—hooray! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding documentation for the global telegram_bot_token configuration in the docs/configuration.md file.
Description check	✅ Passed	The PR description follows the template structure with the checklist completed, documentation checkbox marked, commits signed off, and release notes provided.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}