Guild chunk timeout with large number of members in single shard

[shiftinv]

Summary

The timeout for chunking guilds is len(guilds) * 70, which can be too low if the guilds has a high member count and/or the ws is bottlenecked due to other events.

Expected Results

No warning should be shown, and the timeout should account for the size of the guilds that are currently being waited for.

Actual Results

WARNING [disnake.state._delay_ready:2015] Shard ID 0 failed to wait for chunks from a sub-bucket with length 2

Intents

members + presences

Checklist

• [X] I have searched the open issues for duplicates.
• [X] I have shown the entire traceback, if possible.
• [X] I have removed my token from display, if visible.

Additional Context

https://canary.discord.com/channels/808030843078836254/883342278280745030/1003725784340508732

[onerandomusername]

@shiftinv do you plan on fixing this?

[onerandomusername]

Would it make sense to increase this a bit for now, and properly fix it later?

[shiftinv]

I believe this shouldn't be too difficult to fix, just haven't gotten around to it since it's somewhat of an edge case.