chore/release-v1.10.0: Cut the v1.10.0 release

[vedanthvdev]

What this PR does

Cuts v1.10.0 — the minor bump that closes Phase 1 and Phase 2 of the v2 config redesign.

Two things land in the PR itself:

1. CHANGELOG.md — a new, first-in-repo changelog. The v1.10.0 entry is scoped strictly to the v1.9.9..HEAD window (named outcome + situation on the summary log; deprecation warnings on the three legacy knobs), and the preamble paragraph narrates the full v2 story that landed additively across v1.9.8, v1.9.9, and this release.
2. README "Changelog" section — a short link so the changelog is actually discoverable from the landing page.

The version bump itself is forced by a release-1.10.0 marker tag pushed alongside this branch. Without it, axion-release's default incrementPatch would cut v1.9.10 on merge instead of v1.10.0. The marker tag points at the branch commit — it stays reachable from master after a merge commit, which is how every prior PR on this repo merges, so the release workflow on the post-merge master push finds it and uses 1.10.0.

Why minor, not patch

• Deprecation warnings are a semver signal event. Emitting WARN-level deprecations on configuration knobs that existed for the entire v1 lifetime is the kind of change consumers should see pre-flagged in a version bump, not buried in a patch.
• Named outcome + situation on summary logs is a contract change for anyone greping CI output, even though it's carefully structured to preserve the old substrings used by dashboards.
• Clean identity for the v1.10.x line as "the v2 config bridge" — once v2.0.0 drops and removes the legacy knobs, v1.10.x is the release line operators can pin to while they migrate.

How the release pipeline runs

On merge:

1. Release workflow fires on the master push.
2. It runs ./gradlew release, which finds the release-1.10.0 marker in the ancestry and tags master HEAD as v1.10.0 (skipping the default patch auto-increment).
3. Portal check sees v1.10.0 is not yet published, runs ./gradlew publishPlugins → io.github.vedanthvdev.affectedtests:1.10.0 lands on Gradle Plugin Portal.
4. gh release create v1.10.0 --generate-notes creates the GitHub release with auto-generated notes derived from the merged PR titles (feat/v2-logging: Name outcome and situation on every summary log line #21 v2-logging, feat/v2-deprecations: Warn on legacy config knobs and flip docs to v2 #22 v2-deprecations).

Test plan

• ./gradlew check passes (UP-TO-DATE from the Phase 2 baseline — this PR is docs-only).
• ./gradlew currentVersion reports 1.10.0-alpha on this branch (the -alpha suffix is versionCreator's non-master marker; it strips to plain 1.10.0 on master).
• release-1.10.0 marker tag is pushed and visible on the remote.
• After merge, confirm the release workflow cuts v1.10.0 (not v1.9.10) and publishes to the Plugin Portal.
• After publish, a consumer with id 'io.github.vedanthvdev.affectedtests' version '1.10.0' in build.gradle resolves cleanly.

Changelog preview

The full entry lands in CHANGELOG.md. Short version:

• Added: named outcome + situation on the Affected Tests: … summary log.
• Deprecated: runAllIfNoMatches, runAllOnNonJavaChange, excludePaths — each with a WARN pointing at the v2 replacement.
• Documentation: README examples all v2-native; "Migrating from v1 config" is the single source of truth for operators moving off legacy knobs.