Release v2.10.0

Summary

A Spring Boot starter reduces setting Chronicle up to adding a dependency: a
connected client, artifacts registered before the first request is served, and
an IEventStore ready to inject.

Stacked on #46 — that PR carries the artifact discovery and registration this
starter builds on, and should merge first.

Added

• io.cratis:chronicle-spring-boot-starter — a connected client, artifacts registered before the first request is served, and an IEventStore ready to inject, configured under cratis.chronicle.
• Spring Boot multi-tenancy: the injected IEventStore routes to the namespace the current work belongs to, resolved from a fixed value, an HTTP header, the request subdomain, or a claim on the authenticated principal.
• Spring Boot gives each request an identity taken from the authenticated principal, a causation trail describing the call, and a unit of work that commits on success and rolls back on failure. Each can be switched off on its own.
• Chronicle — the Java-facing Spring bean exposing the everyday operations without coroutines, for Java callers and blocking MVC handlers.
• IEventStoreNamespaceResolver for hosts that decide the namespace themselves.
• Spring Boot samples for Kotlin and Java, each with a walkthrough.
• A guide for Spring Boot support.

Changed

• The README is rewritten around what the client does for you, with Kotlin and Java shown side by side throughout.