Rename coordinates to match JetBrains: libraries/plugin org.thisisthepy, apps io.github.thisisthepy #95

Maintainer decision (2026-10-03): coordinates follow JetBrains 1:1 — libraries and Gradle plugins under org.thisisthepy (like org.jetbrains), shipped apps under io.github.thisisthepy (like com.jetbrains.* app IDs). Code packages python.* stay (they name the language, like kotlin.*/java.*). The domain is owned.

Change:

• Maven group io.github.thisisthepy → org.thisisthepy (python-multiplatform, -ksp, -compose, -gradle-plugin; root allprojects and the library's own).
• Gradle plugin ID io.github.thisisthepy.python.multiplatform.bindings → org.thisisthepy.python.multiplatform.bindings.
• sample app IDs (Android applicationId/namespace, iOS bundle id in iosApp, desktop package) org.thisisthepy.python.multiplatform.demo → io.github.thisisthepy.python.multiplatform.demo; the consumer iOS fixture already uses io.github.
• Gradle attribute names org.thisisthepy.python.version stay (already org).
• Docs/README/SPEC coordinates; release/publishing workflows.

Not changed: Kotlin code packages, the generated table names, Python-visible names (Kotlin packages of the sample's own classes org.thisisthepy.python.multiplatform.demo.* are code packages and stay unless the maintainer says otherwise).

Completion: grep finds no io.github.thisisthepy library coordinate or plugin ID left; publishToMavenLocal produces org/thisisthepy/...; all modules green; consumers (toolchain, pythonx-compose) get follow-up issues with the new coordinates.