Error messages and API docs name methods that don't exist

[zantvoort]

• TemplateProcessor.java:888 and :1203 tell users to "use the whereAny/whereAll builder methods". Neither method exists anywhere in main source; WhereBuilder.kt:33 documents the same phantom convention.
• Seven Kotlin KDoc examples call .getResultList(), the Java name, where Kotlin has the resultList property: PredicateBuilder.kt:40, QueryTemplate.kt:41, QueryBuilder.kt:51, 59, WhereBuilder.kt:44, TypedJoinBuilder.kt:34, 42. WhereBuilder.kt:39 shows where { } where the real method is whereBuilder, and :28/:50 link a QueryBuilder.where lambda overload that does not exist.
• Copy-pasted javadoc: DbTable.java:25 says the annotation specifies the schema name (it specifies the table name), DbColumn.java:27 says "the column, table or view", and Operator.java:50/:55 label EQUALS/NOT_EQUALS as "The EXISTS operator"/"The NOT EXISTS operator".
• Operator.java:118-122: the null guard throws "Column name cannot be null" on the operator's display name, which is never null; the column arrives pre-interpolated in the fourth argument, so a null column silently renders null = ?. Guard the column parameter instead.

[zantvoort]

PR #447 also removes the andAny/orAny predicate combinators this report's doc rewrite surfaced: they were the predicate-level Any variants #372 left behind. and/or now inherit the query root, so a narrow builder combines within the root graph and a joined query combines predicates across entities with the same syntax.