refactor: flip cameleer-common consumer from com.cameleer to io.cameleer

The agent team finished their groupId+package migration; this commit
flips the corresponding consumer side here. Closes the dichotomy noted
in the prior "Registry naming" doc — io.cameleer is now uniform across
all three repos (server, agent, saas).

- 46 .java files: import com.cameleer.common.* → io.cameleer.common.*
- pom.xml + cameleer-server-core/pom.xml: cameleer-common dep groupId
- CLAUDE.md: drop the obsolete "stays on com.cameleer until institutionalized"
  qualifier on Related Project; flip Key Conventions dep coordinate
- cameleer-license-minter/README.md: GAV strings + main-class FQN

Verification: full reactor mvn test -DskipITs — 416 unit tests pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -10,7 +10,7 @@ Cameleer Server — observability server that receives, stores, and serves Camel
 
 - **cameleer** (`https://gitea.siegeln.net/cameleer/cameleer`) — the Java agent that instruments Camel applications
 - Protocol defined in `cameleer-common/PROTOCOL.md` in the agent repo
-- This server depends on `com.cameleer:cameleer-common` (shared models and graph API). The agent repo's groupId stays on `com.cameleer` until that project is institutionalized — this server's own modules are `io.cameleer.*`.
+- This server depends on `io.cameleer:cameleer-common` (shared models and graph API).
 
 ## Registry naming (buildtime vs public)
 
@@ -56,7 +56,7 @@ java -jar cameleer-server-app/target/cameleer-server-app-1.0-SNAPSHOT.jar
 
 - Java 17+ required
 - Spring Boot 3.4.3 parent POM
-- Depends on `com.cameleer:cameleer-common` from Gitea Maven registry
+- Depends on `io.cameleer:cameleer-common` from Gitea Maven registry
 - Jackson `JavaTimeModule` for `Instant` deserialization
 - Communication: receives HTTP POST data from agents (executions, diagrams, metrics, logs), serves SSE event streams for config push/commands (config-update, deep-trace, replay, route-control)
 - URL taxonomy: user-facing data, config, and query endpoints live under `/api/v1/environments/{envSlug}/...`. Env is a path segment, resolved via the `@EnvPath` argument resolver (404 on unknown slug). Flat endpoints are only for: agent self-service (JWT-authoritative), cross-env admin (RBAC, OIDC, audit, license, thresholds, env CRUD), cross-env discovery (`/catalog`), content-addressed lookups (`/diagrams/{contentHash}/render`, `/executions/{id}`), and auth. See `.claude/rules/app-classes.md` for the full allow-list.