fix(maven): Exclude pom checks for JetBrains registry

[zharinov]

Changes

Context

• Closes: extractVersion with postProcessRelease (maven) causes rejected release #32266

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

[rarkins]

@Shegox @remal do you think this matches with the problem you observed?

[rarkins]

The problem is incorrectly described if so, because this solution is unrelated to extractVersion

[zharinov]

Test run: https://github.com/renovate-testing/test-32266-maven-postprocess

[Shegox]

I have been running against a private maven repository on Artifactory and consuming a private package from there. So this wouldn't resolve my specific problem.

Looking a bit more at the initial issue description it might be possible however that they are two different problems.

I will write tomorrow morning a test case for my exact scenario, maybe this helps to narrow it down :)

[remal]

@rarkins I think the issue is that Renovate:

1. Retrives a new version
2. Applies extractVersion
3. Checks that the extracted version exists

I extract version not because it's wrongly retrieved, but because I need it in another format for my build script.

I think what could work if the step 3 was before step 2. But it could break something else. So, the more I think about it, the more I believe that step 3 (checking that the version actually exists) should be configurable. What do you think?