BREAKING CHANGE: Stop transforming custom auth params

[brionmario]

Purpose

This PR addresses the issue reported in asgardeo/asgardeo-auth-react-sdk#208, where the keys passed into the signIn hook are transformed into Snake Case, causing compatibility issues.

Goals

• Resolve asgardeo/asgardeo-auth-react-sdk#208

Approach

The issue was introduced with the changes in asgardeo/asgardeo-auth-js-core#203. The approach involves reverting the specific change that introduced the undesired key transformation.

Before

After

User stories

• Users should be able to pass custom parameters to the signIn hook without having the keys transformed.

Release note

🔥 BREAKING CHANGE: Fixed an issue where custom parameters passed to the signIn hook were transformed into Snake Case, causing compatibility issues.

Documentation

N/A (No documentation impact)

Training

N/A (No training impact)

Certification

N/A (No impact on certification exams)

Marketing

N/A (No marketing impact)

Automation tests

• Unit tests: Included with code coverage information
• Integration tests: Details about the test cases and coverage

Security checks

• Followed secure coding standards in [WSO2 Secure Engineering Guidelines](http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes)
• Ran FindSecurityBugs plugin and verified report? yes
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A (No sample impact)

Related PRs

• PR that introduced the issue: Fix duplicates in authorize search params #203

Migrations (if applicable)

N/A (No migration steps required)

Test environment

Tested on JDK versions, operating systems, databases, and browser/versions as follows:

• JDK: 11
• OS: Mac
• Database: H2
• Browser: Chrome

Learning

The research phase involved an analysis of the introduced changes in asgardeo/asgardeo-auth-js-core#203.