Rate limit is per connection not shard

[MinnDevelopment]

No description provided.

[switchupcb]

@MinnDevelopment @appellation Request to revisit wording as a connection is used as an equivalent to a session. However, a session provides a better representation of the actual rate limit? See the following message for a choice that clarifies the current ambiguity.

[switchupcb]

Per connection implies that the rate limit resets upon a disconnect. It could refer to the initial connection or a session. It's ambiguous because "connection" is currently defined as process in the documentation; not a resource.

Per session implies that a bot application will be limited to 120 RPS per session. For example, an bot application (token) with a session start limit >1 could maintain three different sessions which implies the management of three 120 RPS rate limits.

Per shard — as per b7a7617 (@ssMMiles) — implies that there is a 120 RPS rate limit per shard. For example, there could be a 120 RPS for an application's DM data [Shard 0] vs. an application's Guild Data [Shard 1]. This doesn't make sense because you send a command via WebSocket Session and not via shard (of the session).

Per application implies that a bot application (defined by token) must adhere to the 120 RPS limit regardless of the amount of sessions that are connected. This definition was used before the documentation was updated.

[switchupcb]

#5898