Set up kiit-codes as a standalone multi-project repo

[kishorereddy]

Overview

Sets up kiit-codes as its own repo, copied from the kiit monorepo's core/codes module.
Structured as a multi-project build so an independent sample app can live alongside the library.

Ticket(s)

None

Links(s)

• Source: slatekit/kiit src/core/codes (PR #402)

Dependencies

None — self-contained repo.

Design

• Library code lives in kiit-codes/, matching the repo name (same pattern as kiit-registry).
• samples/sample1 is a separate app that depends on the library, not bundled into it.
• Root build.gradle.kts only declares shared plugins; each subproject configures itself.
• Supports JVM, Android, JS, and iOS, same as before — nothing changed in the library itself.
• README and BUILD.md follow the kiit-registry format, covering usage, build, and publishing.

Notes

• Gradle wrapper jar is committed so ./gradlew works right after a fresh clone.
• kotlin-js-store/yarn.lock is committed, as the Kotlin/JS build expects.

Pending

• No CI workflow yet — build/test/publish are still run manually.
• Not yet published to Maven Central under this repo.

Tests

• All existing unit tests carried over unchanged (Status, Codes, StatusException).
• Verified: lint, static analysis, and JVM tests all pass.
• Verified: full build succeeds for JVM, Android, JS, and iOS.
• Verified: sample app runs and exercises the library end-to-end.