Screwdriver blockby behavior should be at the event level

[VonnyJap]

What happened:

I've noticed that the "blockBy" feature doesn't seem limited to just the current event; it also affects the next event.
a -> b
For example, job 'b' should only execute after both job 'a' has been successfully completed.

However, I've observed that triggering the pipeline twice in succession results in 'old_b' needing to wait for both 'new_a' to finish.

What you expected to happen:

'old_b' should be run immediately after 'old_a' is completed.

How to reproduce it:

N/A

[VonnyJap]

The global-level blockedBy behavior is part of Screwdriver's original design and should be preserved. This is particularly important in scenarios where builds from the same job, running across multiple events, block one another—for example, an older build preventing a newer build from starting.