fix: sdk config client secret in query param

[ArushKapoorJuspay]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Client Secret was being sent in headers instead of being passed as query param for sdk_config API call because of which it was throwing 400

{
    "error": {
        "type": "invalid_request",
        "message": "Missing required param: client_secret",
        "code": "IR_04"
    }
}

How did you test it?

Tested SDK Config API call -

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with  

[github-actions]

🚫 Missing Linked Issue

Hi 👋 This pull request does not appear to be linked to any open issue yet.

Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically.

✔️ How to fix this

• Add a keyword like Fixes #123 or Closes #456 to your PR description or a commit message.
• Or link it manually using the "Linked issues" panel in the PR sidebar.

✅ Tip: You can link multiple issues.
🚫 Note: If only one issue is linked, it must be open for this check to pass.

Once linked, this check will pass automatically on your next push or when you re-run the workflow.

Thanks for helping maintainers! 🙌

[ArushKapoorJuspay]

Another Pr already has been raised for this

[sakksham7]

Remove client secret from headers as well for fetch sdk configs