fix(datasource/npm): respect abortOnError hostRule for registries

[Shegox]

Changes

This PR adjusts the npm datasource to respect hostRules with abortOnError.
This is archived through checking if the http request throws an ExternalHostError and if yes will throw them up.

To keep the existing logic of aborting on registry.npmjs.com it checks if a hostRule with an explicit abortOnError setting exists and only if not we will add a custom hostRule setting abortOnError: true for registry.npmjs.com. This allows as well to explicitly opt-out of abortOnError for registry.npmjs.com with abortOnError: false.

Context

Fixes #13482

Additionally it allows to set abortOnError for custom registries, which is a use-case I currently have.

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
  • testing unavailable custom host with abortOnError: true => aborts run
  • testing unavailable custom host without abortOnError => doesn't abort run
  • testing unavailable registry.npmjs.org without abortOnError => aborts run
  • testing unavailable registry.npmjs.org with abortOnError: false => doesn't abort run

[rarkins]

@zharinov is this change complementary to the refactoring you plan to do?

[zharinov]

Looks so

[viceice]

otherwise LGTM

[renovate-release]

🎉 This PR is included in version 37.267.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.267.1

Your semantic-release bot 📦🚀