feat: abortOnError / abortIgnoreStatusCodes

[rarkins]

This PR adds the ability for users to customize which hosts throw DatasourceErrors and for which HTTP status codes. abortOnError can be used to opt-in certain host types or specific hosts such that they throw DatasourceError and abort the run, while abortStatusCodes allows for the list of status codes to be customized.

Sets groundwork for #5557

[rarkins]

TODO:

• throw for http errors too (ETIMEOUT, etc)
• Convert hardcoded datasource error throwing into hostRules
• Ensure default abortStatusCodes are added to hostRules
• Determine how this should work with DatasourceError and PlatformError. Support throwing either type, or combine them into one such as ExternalHostError, etc?

[rarkins]

@JamieMagee @viceice what do you think about this approach? I think it achieves the flexibility necessary without being too confusing. Even the basic examples given in documentation can be turned into in-built presets to make it simpler still.

[viceice]

I'm fine with this approach. 👍

[JamieMagee]

Yeah, also sounds good to me. I like the composability we gain with hostRules

[rarkins]

Waiting on #6563

[lgtm-com]

This pull request introduces 1 alert when merging 074b693 into 02e6817 - view on LGTM.com

new alerts:

• 1 for Invocation of non-function

[renovate-release]

🎉 This PR is included in version 21.16.0 🎉

The release is available on:

• GitHub release
• 21.16.0

Your semantic-release bot 📦🚀