Purpose

Resolve #1447 by keeping per-commit release-history details out of INFO output while retaining them at DEBUG verbosity.

Rationale

ReleaseHistory emits parsing, exclusion, and destination details once or more for every traversed commit. On large repositories, those records dominate -v output and can exceed CI log limits. They are diagnostic details rather than summaries, so this change moves all six per-commit records to DEBUG while leaving aggregate INFO records, such as the number of previous tags, unchanged.

How did you test?

• added a caplog regression that verifies parsing, exclusion, and addition details are DEBUG while the aggregate previous-tags record remains INFO
• verified the regression fails on the unmodified baseline and passes with this change
• ran the complete release-history comprehensive selection: 19 passed
• ran a real noop CLI comparison: -v emitted no per-commit details, while -vv retained them; aggregate tag counts remained visible
• Ruff check, Ruff format check, production-file Mypy, and git diff --check passed

How to Verify

1. Run the release-history unit test file with --comprehensive.
2. Run semantic-release -v version --noop in a repository with history and confirm parsing, excluding, and adding records are absent.
3. Repeat with -vv and confirm those per-commit records are present.

PR Completion Checklist

• Reviewed and followed the Contributor Guidelines
• Changes implemented and validation pipeline succeeds
• Commits follow Conventional Commits and are separated into source and unit-test commits
• Appropriate unit tests added
• End-to-end coverage evaluated; the existing CLI verbosity mapping is unchanged, and a real noop CLI comparison passed
• Documentation evaluated; no user-facing option or API changed, and -vv retains the existing diagnostic details