Can not install yamlfmt in environment.yml in Windows

[tristan-f-r]

@ntalluri did this work for you after #305? I installed the latest conda env and now get:

[INFO] Installing environment for https://github.com/google/yamlfmt.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Restored changes from C:\Users\agitter\.cache\pre-commit\patch1752252703-32208.
An unexpected error has occurred: CalledProcessError: command: ('C:\\Users\\agitter\\.conda\\envs\\spras\\bin\\go.EXE', 'install', './...')
return code: 2
expected return code: 0
stdout: (none)
stderr:
    go: cannot find GOROOT directory: 'go' binary is trimmed and GOROOT is not set

It looks like the conda installation gave me go.exe and gofmt.exe on Windows but not the full go SDK. I reopening this because Go is broken on Windows for me.

This appears to be an unresolved issue conda-forge/go-feedstock#203

Originally posted by @agitter in #295

Extra note from @ntalluri: This was not caught in the windows "Test conda environment" workflow because it already comes with Go.

[agitter]

Until the upstream issue is resolved, Windows developers can follow these steps:

• conda activate spras
• conda uninstall go (confirm)
• Install go following instructions at https://go.dev/doc/install
• Test installation with go version and go env

[agitter]

Can we revert #305 and remove go from the conda environment? Currently on Windows I have to manually uninstall go every time I update our environment from the yml file.

[ntalluri]

If we revert #305, we should also revert #239. (We should also double check if any other yamlfmt prs relied on go and revert those).

[agitter]

I'm okay leaving #239 to continue having well-formatted yaml. It does mean that we need to update our SPRAS contributing guide for developers telling them to install Go manually. That is another requirement, but it was fast for me to do.

If the upstream issue with go for Windows in conda is ever resolved, we could resume installing go through conda and simplify developer setup.

[ntalluri]

We might need to do this before the tutorial.

[tristan-f-r]

Does the tutorial cover wrapping new algorithms? If not, #332 can circumvent this issue.