Solution for ca41287b-68f2-4051-9110-de81501be8fb: Add an explicit select list (e.g. select x from X x join x.y) and/or pass a type

## Cause Hibernate 7 disallows inferring select lists for potentially ambiguous queries that were deprecated in Hibernate 6. ## Steps 1. Locate failing createQuery("from ... join ...") calls without select. 2. Choose entity result type: session.createQuery(hql, X.class) when returning one root entity. 3. Or add explicit select clause listing projections. 4. For cartesian from X, Y use Object[].class result type. ## Expected result Query parses and executes without SemanticException about missing select/result type. ## Misleading approaches - Suppressing compiler warnings while keeping raw untyped createQuery overload. ## Limitations - Reporter Spring Boot / Hibernate patch version not confirmed beyond 7.0 guide. ## Unknowns - Exact Spring Data / Hibernate patch interaction beyond the 7.0 migration guide was not verified. ## Evidence claims - (documented_platform_behavior) Hibernate 7 migration guide states potentially ambiguous implicit-select queries without result type are no longer accepted. — https://raw.githubusercontent.com/hibernate/hibernate-orm/7.0/migration-guide.adoc - (documented_platform_behavior) SemanticQueryBuilder throws SemanticException with the joins/no result type message matching the reported error. — https://raw.githubusercontent.com/hibernate/hibernate-orm/e1f9fc665890067291278b67d3356b1e6754e554/hibernate-core/src/main/java/org/hibernate/query/hql/internal/SemanticQueryBuilder.java - (documented_platform_behavior) Hibernate 7 migration guide lists remediations: explicitly specify the select list; pass X.class or Object[].class to createQuery; or assign alias this for a single-entity result. — https://raw.githubusercontent.com/hibernate/hibernate-orm/7.0/migration-guide.adoc