Generate typed enums for inline enums in array items

[halotukozak]

Summary

Fixes #74. Inline enums declared directly in array items (or inline on a property) were generated as plain String, losing both the enum values and type safety.

Before

public val measurements: List<String>? = null

After

@Serializable
public enum class ExecuteSpeedTestRequest_MeasurementsItem {
    @SerialName("DownloadSpeed") DOWNLOAD_SPEED,
    @SerialName("UploadSpeed") UPLOAD_SPEED,
}
// ...
public val measurements: List<ExecuteSpeedTestRequest_MeasurementsItem>? = null

Changes

• New TypeRef.InlineEnum variant.
• SpecParser emits InlineEnum for enum schemas that are not named components (named component enums still resolve to Reference). Null enum entries (nullable markers) are filtered.
• ModelGenerator collects inline enums, deduplicates structurally (InlineEnumKey), registers names via the shared NameRegistry, generates an EnumModel, and resolves references — mirroring inline-object handling.
• The duplicated collect → dedup → name → model pipeline for inline objects and enums is unified into collectInlineDefinitions + topLevelTypeRefs.

Tests

• SpecParserInlineEnumTest — parser produces Array(InlineEnum) from the spec.
• ModelGeneratorInlineEnumTest — a typed enum class is generated and the property references it.
• Naming follows the existing inline convention (<Parent>_<Property>Item).

Out of scope (separate follow-ups, noted in #74)

• uniqueItems: true still maps to List (not Set).
• Array default is still dropped (nullable property defaults to null).

🤖 Generated with Claude Code

[github-actions]

Coverage Report

Overall Project	96.5% -0.65%	🍏
Files changed	88.49%	🍏

File	Coverage
InlineCollector.kt	100%	🍏
TypeRef.kt	100%	🍏
SpecParser.kt	95.58% -0.24%	🍏
ModelGenerator.kt	95.18% -0.1%	🍏
InlineTypeResolver.kt	92.82% -2.56%	🍏
InlineSchemaKey.kt	86.75% -6.62%	❌
Utils.kt	80.3% -19.32%	❌