semantic-release does not correctly parse **Bitbucket** repository URL when the repo is cloned via **HTTP**

Current behavior

semantic-release does not correctly parse Bitbucket repository URL when the repo is cloned via HTTP , resulting in non-functional changelog URLs.

NON-working example URL (http://bb.eu.xxx.corp/scm/proj/repo.git) parses {{repository}} as "proj/repo" and {{owner}} as "scm". (Note the /scm is fixed in case of http cloning)
ssh cloned repo working example URL (ssh://git@bb.eu.xxx.corp:7999/proj/repo.git) correctly parses {{repository}} as "repo" and {{owner}} as "proj".

• git remote get-url origin seems to return either http or ssh URLs depending on how you cloned the repo.

Expected behavior

For this example URL (http://bb.eu.xxx.corp/scm/proj/repo.git) the {{repository}} should be "repo" and {{owner}} is "proj".

semantic-release version

24.2.3

CI environment

jenkins

Plugins used

No response

semantic-release configuration

[
  "@semantic-release/release-notes-generator",
  {
    "preset": "conventionalcommits",
    "host": "http://bb.eu.xxx.corp",
    "linkCompare": true,
    "linkReferences": true
  }
],

CI logs

.

Reproduce the parsing with the HTTP Bitbucket URL from the report and trace the repository/owner parsing used for changelog links. Done means the URL yields owner "proj" and repository "repo", producing functional changelog URLs while preserving the working SSH case.