Render object arrays as Kotlin Array<T> in querydsl-kotlin-codegen (#1790)

[seonwooj0810]

Fixes #1790

Problem

querydsl-kotlin-codegen emitted object-array properties (e.g. String[]) using Java array syntax, producing code that does not compile:

val tags: ArrayPath<String[], String> = createArray("tags", String[]::class.java)

String[] and String[]::class.java are not valid Kotlin.

Cause

In Extensions.kt, Type.asClassName() special-cases the eight primitive array types (int[] → IntArray, etc.), but object arrays fall through to the generic ClassName(packageName, simpleName) branch, where the array's simpleName (String[]) leaks into the generated source. asClassNameStatement() had the same gap.

Fix

Map object arrays to the Kotlin Array<T> type and the Array<T>::class.java class literal, while leaving primitive arrays on their dedicated Kotlin array classes (IntArray, ByteArray, …). Object arrays are detected via Type.getComponentType(), excluding the primitive-array full names that asClassName() already handles. The same now generates:

val tags: ArrayPath<Array<String>, String> = createArray("tags", Array<String>::class.java)

Tests

Added EntitySerializerTest.object_array, taken from the reproducer in #1790, which asserts the generated declaration/statement and (via the existing assertCompiles helper) that the output compiles.

mvn -Pno-databases -pl querydsl-tooling/querydsl-kotlin-codegen test
Tests run: 27, Failures: 0, Errors: 0, Skipped: 2 → BUILD SUCCESS

Verification done: (1) no in-flight PR/linked branch for the array bug; (2) no active claim on the issue (only the boilerplate template checkbox); (3) fix touches .kt files only; (4) confirmed the missing object-array case in asClassName/asClassNameStatement on current master; (5) reproduced with the issue's test, which failed before and passes after; full querydsl-kotlin-codegen test suite green with no regressions.

[velo]

Thanks for the focused fix. The production change has a compiling regression test, preserves existing primitive-array behavior and public API compatibility, and introduces no security risk. Required checks are green.