Call blocking events on virtual threads

[masmc05]

As briefly mentioned on discord, bukkit currently doesn't have support for proper async events. Currently events where it is recommended to block the thread (like async configuration event in order to wait for a dialog response) will block a platform thread until the plugin is finished/user decided to respond. As an alternative calling those events from virtual threads makes blocking much cheaper.

CONFIGURATION_POOL is currently used for:

• calling AsyncPlayerConnectionConfigureEvent (potential blocking for dialog response waiting, resource pack response waiting)
• calling AsyncPlayerSpawnLocationEvent (potential blocking for database lookup of a spawn location, no join event happened for preload)

authenticatorPool is currently used for:

• http calls for mojang authentication (guaranteed blocking)
• AsyncPlayerPreLoginEvent (potential blocking for data load as it's first event)
• Profile completion (blocking)
• waiting for PlayerPreLoginEvent to finish (guaranteed blocking if has listeners)

Both have no workload that would require a platform thread, and both benefits from calling the blocking logic in a virtual thread

[Owen1212055]

I agree 100% with making the config phase use virtual threads, I am not sure about the login event just due to HOW long its been around. However, it seems fair, and would be really nice,