Do not check order of indexes when MapConfig is added via dynamic configuration

[k-jamroz]

Index order generally does not matter. Indexes are matched by name and chosen for the query based on the attributes. MapConfigs with different index order should be treated as equivalent.

Reported via community slack: https://hazelcastcommunity.slack.com/archives/C015Q2TUBKL/p1692188601524379

Checklist:

• Labels (Team:, Type:, Source:, Module:) and Milestone set
• Label Add to Release Notes or Not Release Notes content set
• Request reviewers if possible

[vbekiaris]

thanks for the fix @k-jamroz. Should it be backported to 5.3.z, wdyt?

[k-jamroz]

@vbekiaris I think the issue is rather hard to trigger, you have to be creating MapConfig with unpredictable order of IndexConfigs (eg. from hash map), which looks like not the most obvious way to do it. So I would wait with backporting unless this is explicitly requested.