Add workflow for releasing sparkctl binary

[ChenYi015]

Purpose of this PR

Close #1009.

Proposed changes:

• Add workflow for releasing sparkctl binary

Change Category

Indicate the type of change by marking the applicable boxes:

• Bugfix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that could affect existing functionality)
• Documentation update

Rationale

Checklist

Before submitting your PR, please review the following:

• I have conducted a self-review of my own code.
• I have updated documentation accordingly.
• I have added tests that prove my changes are effective or that my feature works.
• Existing unit tests pass locally with my changes.

Additional Notes

[ImpSy]

The matrix here as no impact on the os / arch use since we rely on ubuntu-latest (linux/amd64)

But we could rely on go native capability to build cross-platform binaries by setting GOOS=${{ matrix.os }} GOARCH=${{ matrix.arch }} as env var when running make build-sparkctl

I would also not recommend using matrix in that specific case because It create new runner for each variation and does not reuse the go build cache meaning that time we have to wait a full build time

[ChenYi015]

But we could rely on go native capability to build cross-platform binaries by setting GOOS=${{ matrix.os }} GOARCH=${{ matrix.arch }} as env var when running make build-sparkctl

Make sense. Have added them as job envs.

I would also not recommend using matrix in that specific case because It create new runner for each variation and does not reuse the go build cache meaning that time we have to wait a full build time

It will truly create 4 different runners, but they will build sparkctl binary concurrently, so actually the whole waiting time is shorter.

[ChenYi015]

/assign @jacobsalway @ImpSy

[ImpSy]

/lgtm

[ChenYi015]

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ChenYi015, ImpSy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ChenYi015]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment