fix(ci): do not run set_e2e_requirement_status on unlabeled

[nevermarine]

Description

Do not run set_e2e_requirement_status job on unlabeled action.

Why do we need it, and what problem does it solve?

When the e2e test is successfully finished, the remove_label job removes e2e/run label. But because dev_module_build workflow is triggered on unlabeled events, the workflow is run again and the status gets erased.

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: fix
summary: do not run set_e2e_requirement_status on unlabeled