fix(bot): prevent bot freeze by resetting failed init promise

[Dhereal1]

Problem

If bot.init() failed once (e.g. transient network or config issue), the rejected promise was cached and reused. This caused the bot to stop processing all future updates on that instance.

Fix

• Reset botInitPromise to null on init failure
• Allow subsequent requests to retry initialization
• Preserve single-flight behavior for successful init

Result

• Bot recovers automatically from transient init failures
• Prevents “silent dead bot” state

Testing

• Verified locally with polling mode
• /start responds correctly
• Confirmed bot does not stay stuck after init failure

[staindart]

In your webhook.ts change, you have both a .catch() and a try/catch block. Since bot.init() returns a Promise, the try/catch is actually redundant because async errors are captured by the .catch() or the returned rejected promise.