feat: populate jwt_response.claims

[ckiee]

Related Issues

Part-of: https://github.com/descope/etc/issues/11910

Honestly this feels extraneous with the adjacent sessionToken being a dict with the claims in a non-cookie environment, but it doesn't hurt to be consistent across SDKs.

Must

• Tests
• Documentation (if applicable)

[Copilot]

Pull Request Overview

This PR adds population of the claims field to JWT responses to maintain consistency across SDKs. The change extracts claims from the response body and includes them in the JWT response object.

• Adds claims field extraction from response body to JWT response generation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

Coverage report

The coverage rate went from 97.79% to 97.79% ⬆️

100% of new lines are covered.

Diff Coverage details (click to unfold)

descope/auth.py

100% of new lines are covered (95.67% of the complete file).

[ckiee]

descope/go-sdk#605 (comment)

Not necessary after discussion since the backend will always have the session token and we'd rather protect the user from data inconsistency, then make getting the claims a bit shorter.