feat(some-kotest): Kotest Property Testing Integration

[MessiasLima]

Summary

This pull request introduces the new some-kotest artifact for Kotest property testing, updates Android to re-export the shared Some API transitively, and reorganizes the docs around product-level artifacts and shared concepts.

Changes included:

• Added the new kotest JVM module published as dev.appoutlet:some-kotest.
• Added Arb.some<T>() integration plus tests covering generation, configuration application, and reproducibility.
• Changed some-android to expose some-core transitively with api(projects.core) and added publishing configuration for the Android artifact.
• Reworked the docs, README, and site navigation around shared product concepts (strategies, supported-types, artifacts, and versioned migration guides).
• Added local OpenCode advisor/doc-writer agent definitions and updated AGENTS.md to reflect the current module/artifact structure.

Checklist

• Tests were added or updated when needed
• Documentation was updated when needed

[gemini-code-assist]

Code Review

This pull request restructures the project into multiple Gradle modules (some-core, some-android, and the newly added some-kotest for Kotest property-based testing integration) and configures Maven publishing for the new artifacts. It also updates the documentation and README to guide users through the migration. Feedback on the new Kotest integration highlights a performance bottleneck where someSetup is repeatedly called inside the Arb.sample function; it is recommended to initialize the generator once outside the Arb and override only the seed per sample call.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.