Let maintainers know that an action is required on their side

• Add the label release-required Please cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module) when you request a maintainer to cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)

• Add the label release-blocker Follow-up is required before cutting a new release if a follow-up is required before cutting a new release

• Add the label publish-required Please publish libraries (`Devolutions.Gateway.Utils`, OpenAPI clients, etc) when you request a maintainer to publish libraries (Devolutions.Gateway.Utils, OpenAPI clients, etc.)

• Add the label publish-blocker Follow-up is required before publishing libraries if a follow-up is required before publishing libraries

The change is in f5ef013 commit. I branched off #1329, but since that PR is from a fork, I can't set the merge target to that branch.

So, we should wait for #1329 to be merged first, and then I will rebase this branch to the new master. After this, we will be able to merge it. But it should be fine review f5ef013 commit as it is now.

Looking good! Let’s merge after the other PR 👍

EDIT: PR merged. Can you rebase your branch?

Done