Split workflows into modules

[philnewm]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the enhancement you have in mind and explain what the current shortcomings are?

Workflow like the release_trigger are insanely long yaml files right now (400 lines)

This is not practical to work with anymore.
These workflows should be plit into reusable modules to decrease repetiation and increase visibility.

How would you imagine the implementation of the enhancement?

For the most part each job of a workflow should become its own module.

This means, having input and output values while beeing able to work standalone as an abstract unit.
So the release trigger and initial_release workflow might be able to share many of these modules.

This would make any maintenance way easier.

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

Leaving it as is

Additional context:

No response