initial redirector service implementation

[BenTheElder]

• add Umbrella issue: k8s.gcr.io => registry.k8s.io solution k8s.io#1834 (comment) (with git "Co-authored-by" attribution), and gives it a name: αρχείο (archeío) is roughly? Greek for "registry".
• add a README with some detail
• add makefile + boilerplate scripts adapted from kubernetes-sigs/kind (we've also previously adapted these for kubernetes-sigs/kubetest2 and kubernetes/test-infra)
  • this also includes vendoring gimme from HEAD, which makes the PR look bigger than it is 🙃
• stub in building an image with ko

I'll work more on that last part tomorrow.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder

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

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

[ameukam]

I don't think we need to maintain compatibility for the v1. The old docker clients will be served by k8s.gcr.io.

[ameukam]

/lgtm

[ameukam]

Followup:

• automate image building with cloudbuild
• have presubmits running some tests
• build the infrastructure for it.

[BenTheElder]

#7 for CI
#6 for whoops :-)

Also FYI:
With this makefile you either need shellcheck installed at the latest version (v0.8.0) or docker to run make shellcheck / make verify, the rest require just make/bash/posix and auto manage a go toolchain with gimme (vendored).

Other tools are managed with hack/tools go module, including ko (for distroless image builds without docker), gotestsum (nicer test results + junit for CI), golangci-lint (for linting).

The targets should otherwise be fairly self explanatory / commented, I think ...