Github action with multi-CPU architecture support and multi docker file support

[skabashnyuk]

• Build and push to docker registry Dockerfile under linux/amd64,linux/s390x,linux/arm64,linux/ppc64le
• Build and push to docker registry rhel.Dockerfile under linux/amd64
• Allow to configure with secrets DOCKER_USERNAME, DOCKER_PASSWORD, DOCKER_IMAGE, DOCKER_REPO
• Same workflow for master and prs
• Is able to push tags

Results https://quay.io/repository/skabashn/che-jwtproxy?tab=tags
Synced code with che-incubator/configbump#5

[skabashnyuk]

CC @nickboldt @mkuznyetsov @fbricon @kumarvikas2020

[benoitf]

It is leaving rhel.Dockerfile untouched is it still working ?

[benoitf]

should all cico scripts be disabled/removed as well ? it won't collide ?

[metlos]

LGTM. Vendoring was evil anyway :)

[skabashnyuk]

@benoitf

It is leaving rhel.Dockerfile untouched is it still working ?

Yes, I've checked. It works.

should all cico scripts be disabled/removed as well ?

Don't want to hurry up. Let's live it for some time.

it won't collide ?

Don't know. Need to talk with @mkuznyetsov @nickboldt

[nickboldt]

@skabashnyuk +0. I'm not going to comment on a PR that changes 417 files in a repo for which I'm neither an owner not an expert. If you want my input please make this into a set of several smaller, more manageable PRs.

That said... I don't see any changes to a rhel.Dockerfile similar to what you changed in Dockerfile, so this change might not be reflected in downstream. Is that intentional?

[skabashnyuk]

@nickboldt it has 5 changed files and removed vendor folder are you sure you want me to split it?

[nickboldt]

No, I'm OK with the deleted files since you explained the rationale in Slack. Upgrading my vote to +0.5

But I'm still wondering if you've forgotten to do anything in the rhel.Dockerfile file to match your changes in Dockerfile.

https://github.com/eclipse/che-jwtproxy/blob/a2fcdaedd8dfa4d660e23c5e7b17c07749d22acb/build/dockerfiles/rhel.Dockerfile

If you can explain why these changes are not applicable to downstream (as I suspect is the case), or add changes to the rhel.Dockerfile too, then I'll be +1.

[skabashnyuk]

@nickboldt

• https://github.com/eclipse/che-jwtproxy/pull/30/files#diff-5d421a2eae745dc052d563fba3467293R21-R30 that is about multi-CPU architecture support which is irrelevant to rhel
• Alpine update -irrelevant to rhel
  https://github.com/eclipse/che-jwtproxy/pull/30/files#diff-5d421a2eae745dc052d563fba3467293R57-R66
  https://github.com/eclipse/che-jwtproxy/pull/30/files#diff-5d421a2eae745dc052d563fba3467293R70-R74
• Image labels. Might be relevant. https://github.com/eclipse/che-jwtproxy/pull/30/files#diff-5d421a2eae745dc052d563fba3467293R57-R66

The core and the significant part I believe are identical.