feat(spring): add support for the unwind aggregation stage INTELLIJ-176

[kmruiz]

Description

Checklist

• New tests and/or benchmarks are included.
• Documentation is changed or added.
• Changelog is updated accordingly.
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement).

Open Questions

[github-actions]

Coverage Report

Overall Project	78.87% -0.05%	✅
Files changed	84.26%	✅

File	Coverage
SpringCriteriaDialectParser.kt	88.57%	✅
UnwindStageParser.kt	84.82% -15.18%	✅

[github-actions]

🤖 Benchmark Comparison for chore: add support for unwind

Benchmark	Previous	Current	Change
com.mongodb.jbplugin.jmh.SampleBenchmark.init	2,600,565,477.62 ops/s	2,588,223,764.27 ops/s	-0.47%

[himanshusinghs]

In addition to the parser test, maybe we should extend our current inspection and autocomplete test to also check for cases in unwind.

[himanshusinghs]

I think the method name is a little confusing but the idea of this method isSuitableForFieldAutoComplete is for parsers to check and confirm, based on their understanding, if the provided method call is a good target for autocompleter to add field autocomplete.

So it will most likely have the same logic as canParse but might also differ (for example it does differ in project parser). In this case, I think we can safely defer to canParse.

[kmruiz]

Ah cool, I'll fix it then! I think eventually we will need to add more information to this method then, because not all arguments in a method call expression are suitable for autocomplete. But this is something we can do later.