ci: change to use GitHub actions (backport #239)

[mergify]

Which issue(s) this PR fixes:

longhorn/longhorn#8039, longhorn/longhorn#8503

What this PR does / why we need it:

Special notes for your reviewer:

Additional documentation or context

---

This is an automatic backport of pull request #239 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of a30baa6 has failed:

On branch mergify/bp/v1.5.x/pr-239
Your branch is up to date with 'origin/v1.5.x'.

You are currently cherry-picking commit a30baa6.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .drone.yml

no changes added to commit (use "git add" and/or "git commit -a")

Cherry-pick of 8df21c2 has failed:

On branch mergify/bp/v1.5.x/pr-239
Your branch is ahead of 'origin/v1.5.x' by 1 commit.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit 8df21c2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .github/workflows/build.yml
	modified:   Dockerfile.dapper
	modified:   scripts/package

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   package/Dockerfile
	both modified:   scripts/build

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[innobead]

There is a place to improve the build time for build_push_image.

When running build_build_image, build will be executed first, and it will build the container image locally (only local arch). Building the image will then be executed again in build_push_image, as we are using a few action steps to achieve that to have multiple arches support.

The suggestion will be to consider skipping the container image build in the build step when running build_push_image.

cc @derekbit