reusable workflow for QNX builds

[dcalavrezo-qorix]

add reusable workflows that allow qnx builds, they should be gated ( meaning an approval is needed to trigger them).

[AlexanderLanin]

Early November @nradakovic proposed these (pseudo-code):

jobs:
    build_host_x86-64_linux:
        ...
        uses:  /path/to/cicd_repo/docker-build.yml
        env: # optional
            SCORE_QNX_LICENSE: ${{ secrets.SCORE_QNX_LICENSE }}
            SCORE_QNX_USER: ${{ secrets.SCORE_QNX_USER }}
            SCORE_QNX_PASSWORD: ${{ secrets.SCORE_QNX_PASSWORD }}
        with:
            output_user_cache: "path/to/cache"
            command: "build" or "test" # or whatever we want to support
            targets:
              - "//path/to/target:1"
              - "//path/to/target:2"
            configs:
              - "bl_x86-64_linux"
            options: # for flags
              - "-//path/to/flag"
            exclude_targets:
              - "//path/to/exclude/target:1"

jobs:
    build_host_x86-64_linux:
        ...
        uses:  /path/to/cicd_repo/docker-build.yml
        with:
            output_user_cache: "path/to/cache"
            command: "build" or "test" # or whatever we want to support
            qnx_build: true
            targets:
              - "//path/to/target:1"
              - "//path/to/target:2"
            configs:
              - "bl_x86-64_linux"
            options: # for flags
              - "-//path/to/flag"
            exclude_targets:
              - "//path/to/exclude/target:1"