This is converging the recipes for go from
meta-virtualization and oe-meta-go
I'm still of the opinion that this should be in meta-go, not oe-core...
FWIW I disagree. Go is a popular systems language and we're increasingly supporting a wide-array of systems with OE (from iot to ivi and beyond).
Go is already in wide enough use and duplicated in enough layers that we would be doing folks a favour by including it in OE-Core and our build/test cycle.