fix: add additional session related errors (supabase#30828)

* fix: add additional session related errors

* fix: add link to sessions doc

* fix: update auth error codes table

Author: J0

apps/docs/components/MDX/auth_error_codes_table.mdx

@@ -55,6 +55,8 @@ To supplement HTTP status codes, Supabase Auth returns a string error code which
 | `provider_email_needs_verification`     | Not all OAuth providers verify their user's email address. Supabase Auth requires emails to be verified, so this error is sent out when a verification email is sent after completing the OAuth flow.                                                                                                         |
 | `reauthentication_needed`               | A user needs to reauthenticate to change their password. Ask the user to reauthenticate by calling the `supabase.auth.reauthenticate()` API.                                                                                                                                                                  |
 | `reauthentication_not_valid`            | Verifying a reauthentication failed, the code is incorrect. Ask the user to enter a new code.                                                                                                                                                                                                                 |
+| `refresh_token_not_found`               | Session containing the refresh token not found.                                                                                                                                                                                                                                                               |
+| `refresh_token_already_used`            | Refresh token has been revoked and falls outside the refresh token reuse interval. See the [documentation on sessions](https://supabase.com/docs/guides/auth/sessions) for further information.                                                                                                               |
 | `request_timeout`                       | Processing the request took too long. Retry the request.                                                                                                                                                                                                                                                      |
 | `same_password`                         | A user that is updating their password must use a different password than the one currently used.                                                                                                                                                                                                             |
 | `saml_assertion_no_email`               | SAML assertion (user information) was received after sign in, but no email address was found in it, which is required. Check the provider's attribute mapping and/or configuration.                                                                                                                           |
@@ -66,6 +68,7 @@ To supplement HTTP status codes, Supabase Auth returns a string error code which
 | `saml_provider_disabled`                | Using [Enterprise SSO with SAML 2.0](https://supabase.com/docs/guides/auth/enterprise-sso/auth-sso-saml) is not enabled on the Auth server.                                                                                                                                                                   |
 | `saml_relay_state_expired`              | SAML relay state is an object that tracks the progress of a `supabase.auth.signInWithSSO()` request. The SAML identity provider should respond after a fixed amount of time, after which this error is shown. Ask the user to sign in again.                                                                  |
 | `saml_relay_state_not_found`            | SAML relay states are progressively cleaned up after they expire, which can cause this error. Ask the user to sign in again.                                                                                                                                                                                  |
+| `session_expired`                       | Session to which the API request relates has expired. This can occur if an inactivity timeout is configured, or the session entry has exceeded the configured timebox value. See the [documentation on sessions](https://supabase.com/docs/guides/auth/sessions) for more information.                        |
 | `session_not_found`                     | Session to which the API request relates no longer exists. This can occur if the user has signed out, or the session entry in the database was deleted in some other way.                                                                                                                                     |
 | `signup_disabled`                       | Sign ups (new account creation) are disabled on the server.                                                                                                                                                                                                                                                   |
 | `single_identity_not_deletable`         | Every user must have at least one identity attached to it, so deleting (unlinking) an identity is not allowed if it's the only one for the user.                                                                                                                                                              |