[chore] add go.work to gitignore

[codeboten]

No description provided.

[dmitryax]

Looking at golang/go#53502, it seems beneficial to keep it in repos with many interdependent modules... Why do we want to exclude before trying?

[codeboten]

Looking at golang/go#53502, it seems beneficial to keep it in repos with many interdependent modules... Why do we want to exclude before trying?

I use go work locally and keep avoiding checking those files in, as i was under the impression the correct thing to do was to not check those in. I'm ok with replacing this PR w/ one that checks them in, I really just want a clean local repo 😄

[dmitryax]

SGTM, do we still want to adopt the workspaces and update all the make targets to use it?

[codeboten]

SGTM, do we still want to adopt the workspaces and update all the make targets to use it?

I've not found a way to successfully use workspaces for purposes other than making intellisense happy :D in other words, i'm not sure if there is much to be gained by updating make targets at this point in time.

[mx-psi]

@pellared is working on making crosslink update and understand go.work (see open-telemetry/opentelemetry-go-build-tools/pull/311). We may want to revert this PR once that work is completed.

[pellared]

After playing with Go workspaces for a while I think it is safer to keep go.work and go.work.sum in Git ignore. The go toolchain works a little different. Because Go workspaces are not widely adopted we may encounter bugs (example: golang/go#60126). Therefore I think it is better to make sure that CI does not work with Go workspaces.

PS. I initially wanted to commit go.work as well 😉

CC @mx-psi