Add custom scopes in CreateAuthURL via PKCEConfig

[notable-franco]

When using the onelogin-node-sdk library to integrate oneLogin to our product we ended up with a situation where we needed to add scopes to get access to custom parameters that our application in oneLogin includes. but the library in its current state uses only the openid scope with no way of adding more.
This change allows the library to set custom scopes via the Configure method of a pkce object. these scopes are added after the openid scope (because that is a required scope).

[Copilot]

Pull request overview

This PR enables custom OAuth scopes when creating authorization URLs in the onelogin-node-sdk. Previously, the library hardcoded the openid scope with no mechanism to add additional scopes needed for custom application parameters.

Key Changes:

• Adds optional scopes array parameter to PKCEConfig interface
• Removes hardcoded QUERYPARAM_SCOPE constant
• Constructs scope query parameter dynamically, appending custom scopes after required openid scope

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The inline scope string construction is complex and hard to read. Consider extracting this logic into a separate method like _buildScopeParam(scopes?: Array<string>): string that constructs the scope parameter with 'openid' as the base and appends custom scopes if provided.

[Copilot]

The scopes property lacks documentation explaining its purpose and that 'openid' is automatically included. Add a JSDoc comment to clarify that this array should contain additional scopes beyond 'openid', which is always present by default.

Suggested change

	clientID: string,
	clientID: string,
	/**
	* Additional scopes to request during authentication.
	* 'openid' is always included by default; specify only extra scopes here.
	*/