client: wait for realm+microsoft auth before signaling connect_allowed

[DallasCarraher]

Summary

For auth: 'microsoft' + realms, onReady() — which wires up setProtocol, keepalive, encrypt, play, compress, pluginChannels (client.registerChannel), and versionChecking — only runs after the realmAuthenticate().then(authenticate) promise chain resolves. Nothing signals that delay to consumers, though: client.wait_connect is never set on this path, so mineflayer's loader.js (if (!bot._client.wait_connect) next()) runs plugin injection immediately, before onReady() has executed at all.

Any consumer that pins an explicit version — skipping autoVersion.js, the only other place wait_connect gets set — crashes with bot._client.registerChannel is not a function as soon as mineflayer's game plugin injects, before the device-code sign-in prompt even has a chance to appear. This is the documented, recommended way to use mineflayer in production (see its own lib/version.js/client.ts conventions around never using version: 'auto'), so realm connections are broken for exactly the use case this library is meant to support.

The fix mirrors the existing autoVersion.js idiom exactly: set client.wait_connect = true before the async work starts, emit connect_allowed and clear the flag once it resolves.

Scope: only touches auth:'microsoft' + realms. The direct (non-realm) microsoft branch, offline auth, and mojang auth are untouched.

Test plan

• standard lint clean
• Live-validated against a real Minecraft Realm (Java Edition, protocol 776) using mineflayer's own createBot() with an explicitly pinned version and a real Microsoft account: reproduced the crash on every attempt before this fix (failed within ~1s, before any device-code prompt appeared); after the fix, device-code sign-in, realm resolution, and connection all completed normally and the bot spawned successfully
• No existing test coverage exercises this path (it requires live realm + Microsoft credentials), so I haven't added an automated regression test — happy to sketch one with a mocked Authflow if that's wanted