Utilize graphql-java's AstSorter and AstComparator instead of custom GraphqlQueryNormalizer.

[kyle-winkelman]

Currently, custom logic occurs within GraphqlQueryNormalizer to normalize the order of the fields within the query. I believe this leads to the described limitations.

References

Submitter checklist

• [ ] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
• [x] The PR request is well described and justified, including the body and the references
• [x] The PR title represents the desired changelog entry
• [x] The repository's code style is followed (see the contributing guide)
• [ ] Test coverage that demonstrates that the change works as expected
• [ ] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

[kyle-winkelman]

I would be willing to create further unit tests to prove out that this removes the described limitations, but it would be helpful to know what those limitations are.

Can we trust AstSorterTest to be extensive enough to rely on or should we add more?

[nilwurtz]

@kyle-winkelman Thank you for the PR! I wasn't aware of AstSorter and AstComparator, but I think they are great ideas and definitely worth using. AstSorterTest seems to be sufficiently tested as it is.

After this change, we will can remove the limitations and release this extension as 1.0 soon!