🌱 Workflow pipeline with unit tests

[lentzi90]

What this PR does / why we need it:

This adds a unit test workflow and restructures the github workflows
so that we run golangci-lint and unit tests first. Only when they have
succeded will the pipeline continue with e2e tests.
The goal is to conserve resources and avoid running pointless jobs.
The commit also removes unnecessary permissions and avoids running the
jobs if the PR is a draft.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[metal3-io-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[lentzi90]

Alright that works as expected! Now the workflows do not run on drafts.

[lentzi90]

Oh! They are only triggered on PR opening... Turning this back to draft so I can test also that properly. The workflows should be triggered on editing the PR.

[lentzi90]

/uncc @zaneb @mquhuy @elfosardo @dtantsur @tuminoid @s3rj1k
Sorry for all the review requests. I had to test the "ready for review" functionality by toggling draft multiple times, and each time added more reviewers...

[Rozzii]

/lgtm

[kashifest]

/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kashifest

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 [kashifest]

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

[lentzi90]

/cherry-pick release-0.6

[metal3-io-bot]

@lentzi90: once the present PR merges, I will cherry-pick it on top of release-0.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[metal3-io-bot]

@lentzi90: #1770 failed to apply on top of branch "release-0.6":

Applying: Workflow pipeline with unit tests
Using index info to reconstruct a base tree...
M	.github/workflows/e2e-fixture-test.yml
M	.github/workflows/e2e-test.yml
M	.github/workflows/golangci-lint.yml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/golangci-lint.yml
Auto-merging .github/workflows/e2e-test.yml
Removing .github/workflows/e2e-test-pull.yaml
Auto-merging .github/workflows/e2e-fixture-test.yml
CONFLICT (content): Merge conflict in .github/workflows/e2e-fixture-test.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Workflow pipeline with unit tests
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.