Refactor Scope Handling to String Type in Compliance with OAuth RFC Standards

[vamsii777]

This pull request introduces a significant update to OAuth implementation, specifically focusing on the handling of the scopes property. In alignment with OAuth RFC standards, we have transitioned the scopes property from being an array to a single string. This change ensures compliance with OAuth specifications and enhances the interoperability of OAuth handling.

Changes

• The scopes property across the application, previously an array of strings, has been updated to a single space-delimited string.
• Updated all relevant instances where scopes are processed, parsed, or stored to reflect this change.
• Modified existing tests to adapt to the new string-based scopes property. Tests now validate against a single string rather than an array of strings, ensuring consistency with OAuth RFC recommendations.

Impact

• This change brings OAuth implementation in line with industry standards as specified in the OAuth RFC.
• It simplifies the handling of scopes by treating them as a single string, streamlining our codebase and reducing complexity.
• Existing integrations or custom implementations that rely on the previous array-based approach will need to be updated to accommodate this change.

Background

According to the OAuth RFC, the scope parameter should be represented as a list of space-delimited, case-sensitive strings. This format allows for a more flexible and standardized way of representing scopes, facilitating better interoperability across different systems and OAuth providers.

• Resolves Incorrect Scope Format in API Response: Single String Instead of Array for Multiple Scopes #11