unify woodpecker yaml files

[individual-it]

we are using yaml files in the CI of desktop and reva but I find them confusing to work with because the format is not unified, I think it would be better to have them all look similar

• order of items
• define when section in arrays not lists

- event: [ push , manual ]
  branch: [main, stable-*]
- event: [ pull_request, tag, cron ]

vs

when:
  - branch:
      - main
      - stable-*
    event:
      - push
      - manual
  - event: pull_request
  - event: tag
  - event: cron

[saw-jan]

The general format and order should be as follows for better clarity and consistency:

💡 Tips:

• ALWAYS Use - <value> (block sequence) format. NO [...] inline sequence format
  • helps to add new values to the list easily
• We can use [...] format for a list of very short values like numbers. RUN_PART: [1, 2, 3, 4]
• Add a new line after each section - better readability
• ONLY when: section can use a single value instead of list

ℹ️ These are just guidelines to maintain consistency

variables:

when:
  - event: push # single value
  - event:      # multiple values
    - tag
    - cron

depends_on: # single value
  - pipeline1        
depends_on: # multiple values
  - pipeline1
  - pipeline2

runs_on:
  - success
runs_on:
  - success
  - failure

workspace:

skip_clone: true

matrix:

steps:
  # ALWAYS use "- name: step-name"
  # visualises series execution
  - name: step1
    image: <container-image>
    when:
      - status: success
    environment:
      Env1: Value1
    commands:
      - cmd1
      - cmd2
    volumes:
      - /host-path:/container-path

  - name: step2
    image: <container-image>
    depends_on:
      - <above-step>
    when:
      - status:
          - success
          - failure
    commands:
      - cmd1

services:
  # DO NOT use "- name: service-name"
  # define service under a service name
  # visualises parallel execution
  svc1:
    image: svc-image
  
  svc2:
    image: svc-image