PLAT-1214: Upgrade to Go 1.16

[fraenkel]

Force rootless builds

There is currently no ideal why to detect when we are root but running
rootless.
For now just force rootless builds.

Support token authorization for docker registry v2

See https://docs.docker.com/registry/spec/auth/token/ for more detail

Update dependencies

Minor changes to get things compiling again.
Use embed instead of pkger

Simplify the makefile
Add a precommit target to verify no code generation is needed

[steved]

Tested w/Domino too and LGTM. I'll let @sonnysideup have final say.

[fraenkel]

waiting on kustomize 4.2.0 binaries to appear...

[sonnysideup]

@fraenkel Check out my comments and see what you think. We can have a zoom chat if that's easier.

Re: moving main.go to cmd/forge/main.go, I'm a little curious what your thoughts are here. I was originally thinking that I would produce 2 separate binaries in my upcoming changes:

• controller
• builder

This project really houses two separate applications. Separate apps/CLIs with reused libraries feels like a cleaner design as opposed to the current, dual-mode based on command weirdness we have now. Assuming we go that direction, removing main.go and setting the project up the way you've started makes sense to me. Was this the first step?

[fraenkel]

@fraenkel Check out my comments and see what you think. We can have a zoom chat if that's easier.

Re: moving main.go to cmd/forge/main.go, I'm a little curious what your thoughts are here. I was originally thinking that I would produce 2 separate binaries in my upcoming changes:

• controller
• builder

This project really houses two separate applications. Separate apps/CLIs with reused libraries feels like a cleaner design as opposed to the current, dual-mode based on command weirdness we have now. Assuming we go that direction, removing main.go and setting the project up the way you've started makes sense to me. Was this the first step?

Would prefer separate binaries but it matters little given one image. Although they will be different sizes based on what is pulled in.

The actual impetus was to get embed to work at the root. It created 2 packages at the root so I just moved the one that made the most sense.