1. Base project setup

[ghost]

This PR adds the base project setup with CI workflows and tools.

[ollevche]

Internal tools look pretty nice! I left some questions regarding cross-repo standards

[cam72cam]

So the problem this PR is trying to solve code-wise, is to move all of the complexity of running the different tooling of the project to internal tools? I'm trying to think of other solutions that we could use instead of creating a custom go tool for each lightweight wrapper.

I also have a preference that when we expose cli args to tooling, we keep the flag names the same.

[abstractionfactory]

@cam72cam it's trying to make it simpler to run the tools we also run in the CI. You can now run go generate to take care of all the things that need taking care of and be sure that you are running the same things the CI is running while letting the CI still invoke each tool separately. Personally, I don't want to expose the CLI flags, these wrappers are intended to be run in a standarized way, if you want to run them in a custom way, run them separately. We are using the same scheme in libregistry and it works fine.

An alternative solution could be to create separate folders with only // go:generate lines in them for each tool, so go generate ./... would capture them but CI could invoke each separately. That way we wouldn't need wrappers.