Introduce naming scheme for workflow names and workflow files

[triffer]

Description
This issue should be blocked until #1068 is completed, since the outcome of issue #1068 will influence the work that needs to be done.

Introduce naming scheme for workflow names and workflow files in git to make obvious the responsibility of each workflow.
This should help with better understanding of the responsibility of the workflows and ordering of workflows in the Actions tab

There is a proposal for a naming scheme for the workflow names:

• Main-PR for PR workflows to main branch
• Main for workflows running on the main branch
• Main-Scheduled for scheduled workflows running on main branch
• Release-PR for PR workflows to release branch
• Release for workflows running on the release branch workflows

For many workflows there is a on.workflow_call trigger. This was introduce to prevent silently failing of tests. Therefore we have many workflows that have the workflow_call trigger, but are only run in a specific scope, e.g. PR integration tests for release branches. Those workflows should also be scoped by the name.
To avoid confusion we should also add a prefix for those workflows, since they also show up in the Actions UI.

While creating the issue the main-integration workflow is special, because it runs on main and release branch. The current assumption is, that completing the issue to Improve test runs to avoid redundancy there might be different jobs running on main and release branch and two workflows exist.

Motivation

Fulfill AC Reduce job runs count, ensure all jobs have clear responsibility and meaning from our team goal.

ToDo [Developer]

• ...

PRs

AC [PO]

• Workflow names and file names adapted
• Created follow up issue to adapt workflows in API Gateway

DoD [Developer & Reviewer]

• Provide documentation.

Attachments