[Bug]: Using a port in a url with a private registry prevents auth from working causing a 403

[snakethatlovesstaticlibs]

What happened?

We have an npmrc file with auth specified in ~.npmrc,

It looks kind of like

registry=https://private/api/npm/npm
@thing:registry=https://private/api/npm/npm

In yarn.lock we have URLs that sometimes look like https://private:443/artifactory/api/npm/npm/.... Notice the port.

_get_npm_imports fails to account for this, which means that auth isn't sent, which means requests 403

Version

Development (host) and target OS/architectures:

Output of bazel --version: 7.0.0

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file: rules_js-1.35.0

Language(s) and/or frameworks involved: JS, yarn.lock

How to reproduce

Have a yarn.lock which contains ports in urls that have private registries, see that the home npmrc auth is no longer passed through to the download call

Any other information?

PR coming soon