Handle incorrect git remote

[privatenumber]

Describe the bug

Previously, I was an external contributor to https://github.com/antfu-collective/sponsorkit so my git remotes looked like this:

• origin: my fork
• up: original repo

When I was given permission to do releases, bumpp pushed the tag to origin, which didn't correctly handle the release because it's my fork.

I'm thinking it should cross check that git remote origin matches the repo in package.json and error if not.

Reproduction

N/A

System Info

N/A

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)