Link in commit creates unwanted `closes` message in release notes

Running on a self-hosted GitLab instance, given the following commit:

git commit -m "fix(cache): lock retry" -m "see https://github.com/mike-marcacci/node-redlock/issues/168#issuecomment-2369328838"

Creates

### Bug Fixes
    * cache: lock retry (78e2a9d (https://my-gitlab-domain/my-group/my-project/commit/78e2a9d924586365dceb302cae2746a24ea43839)), closes /github.com/mike-marcacci/node-redlock/issues/168#issuecomment-2369328838 (https://my-gitlab-domain/my-group//github.com/mike-marcacci/node-redlock/issues/168/issues/issuecomment-2369328838)

Note: the (unwanted) link is invalid too https://my-gitlab-domain/my-group//github.com/mike-marcacci/node-redlock/issues/168/issues/issuecomment-2369328838

My apologies if this is the wrong repo (could be semantic-release/commit-analyzer)

Reproduce the reported output in semantic-release/release-notes-generator with the supplied commit message and self-hosted GitLab setup. Trace how the commit body URL becomes a closes reference, and compare whether the behavior belongs here or in semantic-release/commit-analyzer. Done means the external GitHub URL is not converted into an invalid closes link.