fix: programmatically setting the status of the drone builds

[planctus]

PR description

Since the devops contacted could not apparently find the reason for this, i think we can apply this fix on our side, don't see downsides in doing it. In case the problem will get solved on the drone side we we can then remove this.

QA Checklist

In order to ensure a safe and quick review, please check that your PR follow those guidelines:

• I have put the vanilla component as devDependencies
• I have put the specs package as devDependencies
• I have added the components directly used in the twig file (with include or embed) as dependencies
• My component is listed in @ecl-twig/ec-components's dependencies
• My variables naming follow the guidelines (snake case for twig)
• I have provided tests
• I have provided documentation (for the "notes" tab)
• If my local yarn.lock contains changes, I have committed it
• I have given my PR the proper label (pr: review needed to indicate that I'm done and now waiting for a review ,pr: wip to indicate that I'm actively working on it ...)

[kalinchernev]

Had a brief look for possible issues.
In drone drone.fpfis.eu/ all looked fine. Enabled webhook on pull_request in addition to push for just in case, although won't make any big difference. The https://drone.fpfis.eu/hook webhook is still installed on the repository on Github. Nothing wrong on our side and setup.

[planctus]

@kalinchernev , thanks, i'm still in contact with the dev ops to see if they find the reason for this, worst case scenario this "manual" solution seems to work...