glab mr create --fill keeps adding glab-resolved head and glab-resolved base to gitconfig

Checklist

• I'm using the latest version of the extension (Run glab --version)
  • Extension version: glab version 1.31.0-31-g5eae216f (2023-08-01)
• Operating system and version: Debian
• Gitlab.com or self-managed instance? n/a
• GitLab version (if self-managed) n/a (Use the version endpoint, like this: gitlab.my-company.com/api/v4/version)
• I have performed glab auth status to check for authentication issues

Summary

Every glab mr create --fill adds a glab-resolved head and/or glab-resolved base to your remote.

Steps to reproduce

git config --unset-all remote.origin.glab-resolved
glab mr create --fill # select one of your remotes, I pick origin for the test
                      # You don't need to submit an MR, just hit Cancel after selecting the head/base
git config --get-all remote.origin.glab-resolved
# See two entries, head and base
glab mr create --fill # select one of your remotes, I pick origin for the test
                      # You don't need to submit an MR, just hit Cancel after selecting the head/base
git config --get-all remote.origin.glab-resolved
# See four entries, head, base, head and base again

What is the current bug behavior?

It keeps adding head and base to your remotes.

What is the expected correct behavior?

Don't add it!

Possible fixes

I have a patch ready in https://gitlab.com/waterkip/cli/-/tree/glab-resolved?ref_type=heads