component/golang: clear user cache after build

While running tests using all.bash, `$HOME/.cache/go-build/` is
populated with data referencing the build folder. This is problematic
when using shared parts and installing a not pinned software release
multiple times, like it is the case on test node.

A scenario like this can happen:

 - a first succesful build install in `<shared>/golang1.21/<HASH1>`
 - golang1.21 section is changed in a the software release
 - golang1.21 is installed in `<shared>/golang1.21/<HASH2>`, running
   test fails because the cache `<software_folder>/.cache/go-build/` in
   references paths from `<shared>/golang1.21/<HASH1>/.build/go/src`,
   that was used when building the first build and have been removed
   while installing.

This is visible with errors like this:

    2024-03-21 20:52:37,214 INFO     slapgrid_sr: 2024-03-21 20:52:37 slapos[23849] INFO vet: can't parse raw cgo file: open ../../../../a984f246a1b2789081965ab5c05674a8/.build/go/src/net/cgo_linux.go: no such file or directory
36 jobs for master in 0 seconds
Status Job ID Name Coverage
  External
passed Cloudooo.UnitTest-Master

00:16:33

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

01:26:32

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster.Master

08:04:33

passed SlapOS.Eggs.UnitTest-Master.Python2

00:14:44

passed SlapOS.Eggs.UnitTest-Master.Python3

00:15:40

passed SlapOS.Eggs.UnitTest-Master.Python3Next

00:15:59

failed SlapOS.SoftwareReleases.IntegrationTest-Master

08:47:04

passed SlapOS.Theia.ResilienceTest-Master-ERP5

07:16:11

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:31:44

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

07:44:45

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

01:31:07

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

01:27:37

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster

01:29:54

passed ERP5.StandaloneDeploymentScriptTest-Debian.Buster.Master

10:51:23

passed SlapOS.Eggs.UnitTest-Master.Python2

00:14:12

passed SlapOS.Eggs.UnitTest-Master.Python2

00:31:53

passed SlapOS.Eggs.UnitTest-Master.Python2

00:17:54

passed SlapOS.Eggs.UnitTest-Master.Python2

00:15:51

passed SlapOS.Eggs.UnitTest-Master.Python2

00:19:14

passed SlapOS.Eggs.UnitTest-Master.Python3

00:37:08

passed SlapOS.Eggs.UnitTest-Master.Python3

00:15:56

passed SlapOS.Eggs.UnitTest-Master.Python3

00:18:05

passed SlapOS.Eggs.UnitTest-Master.Python3

00:29:40

passed SlapOS.Eggs.UnitTest-Master.Python3

00:37:14

passed SlapOS.Eggs.UnitTest-Master.Python3Next

00:38:58

passed SlapOS.Eggs.UnitTest-Master.Python3Next

00:36:40

passed SlapOS.Eggs.UnitTest-Master.Python3Next

00:30:20

passed SlapOS.Eggs.UnitTest-Master.Python3Next

00:15:45

passed SlapOS.Eggs.UnitTest-Master.Python3Next

00:41:44

failed SlapOS.SoftwareReleases.IntegrationTest-Master

08:35:49

failed SlapOS.SoftwareReleases.IntegrationTest-Master

10:31:28

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:42:37

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:45:56

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster

00:38:19

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

07:06:18

passed Wendelin.StandaloneDeploymentScriptTest-Debian.Buster.Master

09:56:24