Auth Customization Options

[AS1100K]

What this PR adds?

This PR addresses and closes the issue #130. It introduces two new functions in azalea_client::Account:

• microsoft_with_custom_client_id_and_scope
• with_microsoft_access_token_and_custom_client_id_and_scope.

This PR will allow the developer, to customize the client_id and scope, or use the nintendo switch one. Also, some other functions in auth.rs like refresh_ms_auth_token, get_ms_link_code, interactive_get_ms_auth_token, etc. are modified and takes some extra parameters now. See the changes in auth.rs for more information.

Backwards Compatibility?

The existing functions microsoft and with_microsoft_access_token will maintain their current functionality. However, their implementations have been refactored to depend on the new functions microsoft_with_custom_client_id_and_scope and with_microsoft_access_token_and_custom_client_id_and_scope to avoid code duplication and facilitate easier maintenance.

[1zun4]

This is great, but you are missing two important options:

• RpsTicket format (see CCBlueX@ca3e419)
• Scope (see CCBlueX@2b7484a)

If you are using your own ClientID, these changes are also mandatory. Otherwise this option is useless. I saw that you added a custom scope, but then removed it as it was apparently not needed? What is the reason for this? - d2bb6f4

[AS1100K]

I saw that you added a custom scope, but then removed it as it was apparently not needed? What is the reason for this? - d2bb6f4

I removed the custom scope because that time i thought, that modifying permissions might not be required but rethinking it now, i realize that how can this be useful. Like you liquidboune client_id only works with other scope i.e. not the default one. Also, may be you can take extra permissions and integrate your bot with that.

I will add custom scope and RpsTicket format and commit the changes

[veronoicc]

I just looked trough it an saw a lot of parameters with &'static str, and to my knowledge getting somethink as an &'static is not really possible (unless with a hardcoded str in this case) without leaking memory. Maybe using a non 'static str here is better?

[veronoicc]

Meant fields in the AuthOps struct mb

[mat-1]

Thank you for making this, I'm sorry for taking so long to get to it. This looks good, the main thing I think should be changed is using Option<&str> instead of &str for all the public functions that take a client_id and scope. I can resolve everything here tomorrow (I'm going to sleep after writing this) unless you want to.

By the way, I recommend you also run cargo fmt to standardize the formatting on some of the code.