fix(config): warn if registryUrls is set at top-level in config

[RahulGautamSingh]

Changes

Context

Please select one of the following:

• This closes an existing Issue, Closes: Add a config warning when overriding manager registryUrls #41663
• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

• No — I did not use AI for this contribution.
• Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
• Yes — substantive assistance (AI-generated non‑trivial portions of code, tests, or documentation).
• Yes — other (please describe):

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests, but ran on a real repository, or
• Both unit tests + ran on a real repository

The public repository:

[viceice]

this is not what I had in my mind to fix the issue. it's nearly same as the original PR, where I told that's the wrong solution.

there should be config validation warning instead to not use registry urls at top level config.

later it should be an error because it will almost always cause errors

[jamietanna]

We also need to warn if defaultRegistryUrls

[viceice]

add same for defaultRegistryUrls

[viceice]

why duplicate tests?

[RahulGautamSingh]

why duplicate tests?

one for global config test another for repo config

[viceice]

ok, I don't see a benefit because the check is always done but ok

[github-actions]

🎉 This PR is included in version 43.56.1 🎉

The release is available on:

• GitHub release
• 43.56.1

Your semantic-release bot 📦🚀