v0.2.3

Bugfix release.

• Unwrap Optional returns in generated Kotlin bridges. swift-java binds a Swift T? return as CompletableFuture<Optional<T>>, but the emitter annotated the bridge method as T? and returned the awaited value unchanged, so the generated source did not compile. Optional returns now append .orElse(null), alongside the existing .toByteArray() / .toList() conversions. Surfaced by the first optional-returning @AndroidBridge method, QuickCreateClient.latest() (#5).

Known limitations, unchanged by this release: [T]? and Data? returns still emit the wrong conversion, and optional primitives would need OptionalLong/OptionalInt/OptionalDouble handling if swift-java binds them that way. No bridged method hits either case yet.