A not too uncommon scenario, especially around rampdown, is that the bug fixVersion doesn't match the .jcheck/conf version when a PR is integrated, which results in an unwanted backport being created. To help users avoid this happening, we could add a warning in the buglist in the PR body. The warning would be printed if the bug is still open and has a fixVersion set, and this fixVersion is different than the version in the combined .jcheck/conf (the one in the source branch).

A drawback to this solution is that we don't have a way of automatically reacting to a change in .jcheck/conf in the target branch. If the user knowingly set the fixVersion to 23 in anticipation of the rampdown fork for JDK 22, but opened the PR before that fork. The warning would be printed. After the fork happens and the .jcheck/conf version is updated to 23 in the target (master) branch, the bot would not automatically re-evaluate unless something else triggered it. This could cause confusion with users.