Cancelled RelWithDebInfo builders trigger autobake builders

Synopsis
This is a known behavior because the usual chain is that a RelWithDebInfo builder
will trigger the sibling autobake builder (which produces packages).

The triggering step was set to always run. As far as I remember, there were two primary reasons for it:

• a test failure during RelWithDebInfo MTR, shoudn't block producing packages
• it was used as a mechanism to quickly trigger an autobake builder by cancelling the parent builder

Effect
MDBF-1200 implementation can't be aware of any side-effects
inflicted by a cancel event. I.e. can't be aware that further builds are triggered as a consequence of a cancel event.

Proposed solution
Retain the behavior of triggering autobake builders if there's any test failure, so we don't block producing packages. It is up to the development team to decide if these packages are in a good enough shape for release.

Then, avoid triggering the autobake builder during a cancel event.