Hello Guix!

After intitiating go-team branch (inspired by the rust-team) I started
pushing reviwed patches to it, which may require a full Golang rebuild.
My future plan is to update the existing Golang ecosystem to recent
versions, as most of the packages are quite dated (2-5 years old).

As an intial work golang-*.scm submodules are introduces and some
packages were extracted from golang.scm and placed into logical modules.

- golang-build.scm
- golang-check.scm
- golang-compression.scm
- golang-crypto.scm
- golang-web.scm
- golang-xyz.scm

I have CC'd Troy and Artyom as they are actively working on Golang updates.

Following these threads:
- https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00026.html
- https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00128.html

I might need some guidance on the following topics:
- Do I need to rebase to master or merge master into go-team while
  working on it?
- What is the approximate merge into master cycle?
- Do I need to send patches to guix-patches@gnu.org even if I intend to
  push them to the go-team branch?

After reviewing:
- #69205 [PATCH] gnu: Add go-1.22 and its standard library.
- #68300 [PATCH] gnu: Remove go-1.14.
- #69015 [PATCH 0/2] Deprecate the go-etcd-io-bbolt variable,

I rebased on the latest master, then merged master, and finally pushed
to the go-team branch.

--
Oleg