fix(config): encrypted field validation

[RahulGautamSingh]

Changes

• Throw error if encrypted field found without privateKey & RENOVATE_X_ENCRYPTED_STRICT=true resulting in a config issue being raised

Context

• Ref: When encrypted data is found, and no privateKey, then a config error should be raised #33224

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

1. Self Hosted:

• Encrypted Config in the root config
• Encrypted Config within hostRules
• Encrypted Config in preset

2. Mend Hosted (with MEND_HOSTED=true in env)

[viceice]

this is a breaking change, we should do it in a major version bump

[justo-mend]

@RahulGautamSingh Some tests are failing. Are you able to get them to pass?

[justo-mend]

Thanks @RahulGautamSingh

[rarkins]

Tested on real repo?

[RahulGautamSingh]

Tested on real repo?

Yes, linked in description

[RahulGautamSingh]

Also, don't think it's breaking anymore.

[renovate-release]

🎉 This PR is included in version 39.91.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[justo-mend]

Thanks @RahulGautamSingh !