👻 make release workflow callable

[pranavgaikwad]

Fixes #520

Here is an example of a calling workflow that can use this workflow. It runs this workflow to build Kai binaries for all platforms and does its own things on the same platforms:

name: test

on:
  workflow_dispatch:

jobs:
  kai_build:
    uses: konveyor/kai/.github/workflows/build-and-push-binaries.yml@main

  plugin_build:
    name: plugin build
    needs: kai_build
    strategy:
      matrix:
        runs_on: ${{ fromJson(needs.kai_build.outputs.matrix_info) }}
    runs-on: ${{ matrix.runs_on.os }}
    steps:
      - name: Download kai binaries
        uses: actions/download-artifact@v3
        with:
          name: kai-rpc-server.${{ env.OS }}-${{ env.OS_ARCH }}.zip
          path: kai-rpc-server.${{ env.OS }}-${{ env.OS_ARCH }}.zip
      - name: Build and package the IDE plugin
        run: | 
          # do whatever you need to do to build your own thing

[pranavgaikwad]

This will help address issues like konveyor/editor-extensions#156.

[djzager]

Just one comment. Otherwise it lgtm.

[pranavgaikwad]

Discussed this offline with @djzager...we need to update this PR to include the bundle for all platforms. going to move this to draft until I add that piece here

[sjd78]

Any way to make this an action instead of a reusable workflow? That way it can integrated better into other PR workflows as a simple step instead of chained runs?

@djzager -- Do you see any advantages for doing it that way over the reusable workflows?

Edit: Now I see the matrix of all the platforms -- yeah not sure that is doable as an action. Oh well.

[djzager]

lgtm