Add type-safe property paths overloads (#2126)

[emilienbev]

Fixes #2126

• You have read the Spring Data contribution guidelines.
• There is a ticket in the bug tracker for the project in our JIRA.
• 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).

[mp911de]

This is a great start. I suggest to consider using <T> someMethod(TypedPropertyPath<P, ?>... paths) instead of TypedPropertyPath<?, ?> to constrain the originating entity type to a single type T. The context is e.g. distinct(Person::getName, Person::getAge) where you would likely want to avoid property references to other entities such as distinct(Person::getName, Order::getId). distinct(Person::getName, TypedPropertyPath.of(Person::getOrder).then(Order::getId) would still work because T is in both cases Person as the origin entity.

[mp911de]

Introducing <T> to distinct(TypedPropertyPath<T, ?>... distinctFields) allows to limit property paths originating in the same type. This e.g. prevents distinct(Person::getName, Order::getName) as both properties come from different entities.

[mp911de]

Constraining to R could make sense.

[mp911de]

This pull requests is fine, thanks for addressing earlier comments.