Fix false cycle detection for generic types with different type arguments.

[kamilkrzywanski]

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

Summary

Fixes a spurious cycle detection in MongoPersistentEntityIndexResolver.CycleGuard.Path when the same generic type appears more than once with different type arguments (for example Selection<FruitBasket> and Selection<String>).

Previously, cycle detection relied on PersistentProperty.equals(), which is based on the reflected field and therefore collapses parameterized owners that share the same raw type. That stopped index resolution early and caused nested @Indexed fields to be ignored, with a misleading Found cycle log message.

Cycle detection now compares the property name together with the owner's resolved TypeInformation, so:

• distinct type arguments are not treated as a cycle (nested indexes are discovered)
• genuine recursion through the same parameterized type still stops as before

Related issue

Closes #5213

Test plan

• Added PathUnitTests for same property name on generic owners with different / same type arguments
• Added MongoPersistentEntityIndexResolverUnitTests covering the MongoPersistentEntityIndexResolver - Found cycle for generic types using different type params #5213 repro (FruitShop) and a genuine generic cycle (GenericTreeDocument)
• ./mvnw -pl spring-data-mongodb -Dtest=PathUnitTests,MongoPersistentEntityIndexResolverUnitTests test — 101 tests, 0 failures