Commit range is including incorrect number of commits

**What happened**:
Chronical is identifying the correct commit range to search:
```
[0000] TRACE searching commit range since=04a55885ee162ec00548ec39df68c5b62cf213b5 until=1d013affc27ff04c45411183443def13ca136088
```
```
➜ grype git:(pipeline-parity) ✗ git rev-list --ancestry-path 04a5588..1d013a
1d013affc27ff04c45411183443def13ca136088
7c7afa27d3ec9ee550c13b5b81daa53e29ae0a87
adad97628e7adfc3ad690ecefe8643285d2d1b06
```

However it's computing 862 commits to examine rather than the 3 seen above
```
DEBUG release comprised of 862 commits
```

**What you expected to happen**:
I expected 3 commits to appear in the release

**How to reproduce it (as minimally and precisely as possible)**:
There is an open grype branch called `pipeline-parity` if you pull from head and run `make changelog` this can be reproduced

**Anything else we need to know?**:

**Environment**:
`osx`

- Output of `chronicle version`:
```
Application: chronicle
Version: 0.6.0
BuildDate: 2023-02-08T16:24:20Z
GitCommit: cfbdb0791a8aaaf00b912e6725ea84d40ed0dc30
GitTreeState: clean
Platform: darwin/amd64
GoVersion: go1.17.13
Compiler: gc
```

Check the open grype pipeline-parity branch and run make changelog to reproduce the 862-commit result. Compare the generated range with git rev-list --ancestry-path 04a5588..1d013a; done means the release contains the three commits shown in the issue rather than 862.

Written by the indexing model from the issue text.