jenkins pipeline falsely reports "no changes" in the build following a failure

[Caio Volpato]

## Brief Description:

After a failed Jenkins pipeline, the next build wrongly reports as "no changes", skipping the build as if the failed pipeline was successful.

## Severity

Major: It's still possible to force the pipeline to trigger the build as a workaround

## Steps to Reproduce

1. Trigger a pipeline that fails
2. After the previous pipeline finishes, trigger a new build

The build is skipped, reporting "no changes"

## Expected Behavior

"no changes" should only be applied if the build was successful.

## Actual Behavior

"no changes" are reported after a failed pipeline

## Reproducibility

100%: considering the Jenkins pipelines repository.

## Commit

this issue was last tested at master on https://opendev.org/starlingx/jenkins-pipelines/commit/cdf247f4d69ecb257c44b40783a491c838120e7d

## Workaround

As a workaround the pipeline can be triggered with force so it always run, even if the last pipeline failed

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/jenkins-pipelines/+/920840