Upgraded remix-auth-oauth2 to latest version (2.3.0)

[ElementUser]

Issue Link: #1852

Description of Changes

Upgraded remix-auth-oauth2 to latest version (2.3.0)

• Refactored OAuth2Strategy constructor fields to the ones mentioned in the official documentation: https://github.com/sergiodxa/remix-auth-oauth2?tab=readme-ov-file#directly

===

Note: will require a rebuild & reupload of the bun lock file after merging other Pull Requests that contain dependency changes.

[ElementUser]

@Sendouc note: I couldn't actually test the auth changes (since I don't develop Discord bots & don't know how to leverage the auth flow in the app). It may be best if you test the changes since you already have everything set up to do so - I've made all the refactoring changes I can in the code to follow the latest convention/syntax from the official documentation without VSCode giving me typing/non-existing argument errors

So in theory all you need to do is just test it on your end & see if it works

[Sendouc]

Hmm seems like something else might be needed

[ElementUser]

Hmm seems like something else might be needed

Thanks for testing @Sendouc!

I did some issue lookups in the remix-auth-oauth2 repo & found this: sergiodxa/remix-auth-oauth2#94

Since v2.1.0, the default authentication strategy was set to request_body. I took a look at the Typing for the OAuth2StrategyOptions options based on the linked issue above, and found this in the index.ts file:

/**
     * The method to use to authenticate with the Identity Provider, this can be
     * either `http_basic_auth` or `request_body`.
     * @default "request_body"
     */
    authenticateWith?: "http_basic_auth" | "request_body";

So request_body is the default auth method selected - does Discord/your app use http_basic_auth to authenticate? If so, we can try adding in authenticateWith: "http_basic_auth" and see if that fixes it. Otherwise, I don't know what else to do at the moment unless I can get the auth flow set up locally