Resolve is-prefixed Boolean property paths against the JPA metamodel

[SHEOMM]

Closes #4303

A Kotlin Boolean property named isActive is exposed to Spring Data as isActive, while a JPA property-access mapping derives the metamodel attribute active from the isActive() getter. As a result, findByIsActiveTrue() parses successfully but renders an invalid JPA path.

The parsed segment is now resolved against the JPA metamodel first. If no direct attribute exists, the decapitalized name is used only when the metamodel attribute is read through the same zero-argument boolean or Boolean getter. Direct attributes such as a field-access isActive retain precedence, so this does not introduce general accessor-name aliasing.

The change covers JPQL and Criteria derived-query paths, with regression tests for direct-attribute precedence, nested paths, keyset use, and an unrelated getFoo accessor.

• 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).