Ordering fix comparejson

[harshitashankar]

Tests were failing intermittently because Go's map iteration order is random by design, which meant that the order of nested objects could vary between runs. By sorting the keys before iteration, we can ensure consistent order that matches the test's expectations.

Fixes #17, #16

[keploy]

Keploy failed to create test cases for this PR. For retrying, please click here

[Hermione2408]

@harshitashankar, can you please send me the sample app with which you tested this change.
Also, we do have IgnoreOrdering flag in keploy open source which would ignore the ordering of the json map

[harshitashankar]

@harshitashankar, can you please send me the sample app with which you tested this change. Also, we do have IgnoreOrdering flag in keploy open source which would ignore the ordering of the json map

Verified using this UT- https://github.com/keploy/jsondiff/blob/main/jsonDiff_test.go#L677-L691
Reg ignoreOrdering flag - I checked this. Looks like ignore-ordering flag is not used in the jsondiff comparision.
I could find only one usage of this flag which was here
https://github.com/keploy/keploy/blob/main/pkg/matcher/utils.go#L943
its not being passed to interactions with jsondiff

Let me know if you think something else also needs to be tested.

[Hermione2408]

It looks good to me!