Auto treats maintenance release as the latest when calculating default branch releases

**Describe the bug**

**To Reproduce**

1. Make a release on a branch configured for `versionBranches` (ex. if on V3, make a merge to `version-2` that bumps the semantic version)
2. Make a release on the default branch that bump the version
3. Observe that the version created for `version-2` branch was used to calculate the latest release

In our case, the above decided to apply a Major release of v4

**Expected behavior**

A given Auto release should calculate the latest release made _from the branch it is releasing_. In our case, I would expect it to have ignored releases to `version-2`

**Environment information:**

```txt
Environment Information:

"auto" version: v10.32.1
"git" version: v2.30.1 (Apple Git-130)
"node" version: v14.17.5
GHE version: v2.22.7

Project Information:

✔ Repository: (Enterprise)
✔ Author Name: (Enterprise)
✔ Author Email: (Enterprise)
✔ Current Version: v4.0.0
✔ Latest Release: v3.11.1 (NOTE: we tweaked this after the fact)

✔ Labels configured on GitHub project

GitHub Token Information:

✔ Token: [Token starting with xxxx]
✔ Repo Permission: admin
✔ User: (Enterprise)
✔ API: (Enterprise)
✔ Enabled Scopes: (Enterprise)
✔ Rate Limit: (Enterprise)
```

**Additional context**

N/A