We discovered that cancel-in-progress only controls
in-progress jobs. Which means that pending jobs will _always_
be cancelled regardless. There is an open discussion:
https://github.com/orgs/community/discussions/5435
which was closed saying this is how the feature is designed.
We try to work around this by refactoring into separate reusable
workflows and having concurrency only for PR workflows.
```release-note
NONE
```
Co-authored-by: Mattermost Build <build@mattermost.com>
Mattermost build was a confusingly named workflow. Changed it
to Server CI to make it consistent with Webapp CI.
Also changed the filenames.
```release-note
NONE
```
We are disabling uploading e2e artifacts to mattermost dockerhub repository.
This was temporary, to help with the migration to the new repo, of all sourounding services.
Ticket: https://mattermost.atlassian.net/browse/CLD-5614
We are defining the workflow directive to for `Artifacts generation and upload`/cd/Download artifacts step.
To be the workflow_id from the calling workflow
Signed-off-by: Akis Maziotis <akis.maziotis@mattermost.com>
