feat: Adding Custom OAuth 2.0 Scopes

[Hugo1307]

Description:

Previously, we were requesting all the available OAuth Scopes by default. After this PR it is possible for a developer to choose the OAuth Scopes he needs when he is creating an Authentication Token using the SDK.

What Changed:

• Created the OAuthToken interface and changed the implementation class name to "OAuthTokenImpl".
• Created an OAuth Token Builder so the developer can build the token with his parameters easily.
• Removed the Old Way to create an OAuth Token (using the .create() method) [BREAKING CHANGE].
• Refactored all the OAuth-related classes to a new package. [BREAKING CHANGE].
• Added Unit test to verify the OAuth Token Builder is working as expected.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c94a32f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Hugo1307]

Although Breaking Changes are not ideal, they are necessary in this case to keep the code more organized.

[DevSlashRichie]

Looks great. Maybe we should find a way to add the static names of the scopes.

[Hugo1307]

Looks great. Maybe we should find a way to add the static names of the scopes.

What do you mean by Static Names of the Scopes @DevSlashRichie? Do you want me to add something like "Wallet Read" in the WALLET_READ enumerator?