fix array fqdn bug and add unit tests for JsonNodeMapper

[bettyand]

Description

I noticed a bug while working on adding element metadata to make the data more searchable. I am raising a PR for this before continuing so it will be easier to review.

The bug specifically applies to top-level arrays, which is probably why it wasn't noticed sooner, but could be a problem if using this library to audit collections. The index was being added to the fqdn twice, creating confusing data and potential comparison issues. This PR enhances the JsonNodeMapper to improve handling of JSON arrays and ensure accurate FQDN generation with proper array indices. The changes include:

• Added comprehensive test coverage for nested array structures
• Fixed array index handling in FQDNs to maintain correct grouping
• Added a helper method to improve readability and stay DRY

The changes maintain backward compatibility while adding more robust handling of complex nested structures.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have added examples for the new scenarios in the relevant modules

[ankur4u007]

Just few comments, LGTM otherwise.

[bettyand]

comments addressed, ready for final review

[bettyand]

added some explicit list order tests as suggested by Kunal

[d4rk8l1tz]

@bettyand changes look good.
Question. Have we built a jar with these commits and tested it with an existing client implementation in staging yet or are we waiting for this to merge ?

Closing this since its been reviewed

[vasanthm7]

Looks good to me