software/theia: Do not activate Go workspace

Before this commit, the Go workspace was always activated before
launching the Theia shell and starting the embedded supervisord.

This in turn added the gcc installed by Theia to the PATH, meaning
that nested instances would be compiled with Theia's gcc instead of
the system gcc, making the compilation outcome dependant on Theia.

With this commit, the gcc resolved by PATH is now the system one.

software/theia/buildout.hash.cfg

@@ -15,7 +15,7 @@
 
 [instance-theia]
 _update_hash_filename_ = instance-theia.cfg.jinja.in
-md5sum = a4211295ecd3919b61abbcd51085971f
+md5sum = 79c340ec9f4af948723ef5201b311f45
 
 [instance]
 _update_hash_filename_ = instance.cfg.in

software/theia/instance-theia.cfg.jinja.in

@@ -306,9 +306,6 @@ mode = 0700
 template =
   inline:
   #!/bin/sh
-  . ${gowork:env.sh}
-  # reset PS1 from gowork
-  export PS1='$ '
   export HOME=$${buildout:directory}
   export PATH=${python-language-server:location}/bin:${java-jdk:location}/bin:${cli-utilities:PATH}:$HOME/.cargo/bin:$PATH