ref: optimized the payment_experience object

[Pradeep-kumar1202]

Type of Change

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

Description

Before : Every time the SDK wanted the experiences for one payment method, it re-scanned the entire sdk-config list from scratch — filter the methods, flatten their sub-types, filter again, flatten the rules, then dedup. The one real caller does this inside the /client response parser.

After : The config is walked once, producing a dictionary from "payment_method:payment_method_type" to its experience list. Answering the question for a method becomes a single O(1) dictionary lookup. The scan cost is paid once per parsed sdk-config instead of once per payment method

• Doesn't effect web repo independent re-usable func
• replace the per-lookup sdk-config scan with a build-once payment-experience index

How did you test it?

Impact on Mobile and Web Repositories

Outline steps taken to ensure compatibility with consuming repositories:

• I tested the submodule changes in the mobile repository.
• I tested the submodule changes in the web repository.
• I updated the corresponding documentation in both repositories, if applicable.
• I confirmed the changes do not introduce regressions in either repository.

Checklist

• I reviewed submitted code thoroughly.
• I ensured the changes are compatible with both mobile and web repositories.
• I communicated potential breaking changes, if any, to the relevant teams.