chore: remove go workspace, handle them personal to each developer

[StarpTech]

Motivation and Context

Introduction

Although go workspace has been built to simplify managing multiple modules in a single codebase, we run into couple of very serious issues that we were not able to solve deterministically.

One example: We upgraded a dependency that is not used in any other Go module. This upgrade had the effect that another module dependency was upgraded. Due to this behaviour it was impossible to understand the dependency tree because the change was not reflected in the mod or sum file of any module. Luckily, our CI has catched this before it become a serious issue.

Conclusion

We used workspaces the wrong way. Meanwhile, community has built an opinion around the usage of Go workspaces. Go workspaces should be handled as personal to each developer and therefore not be committed.

• Update .gitignore SeldonIO/seldon-core#4676
• proposal: ref/mod: mention whether go.work files should be checked into VCS golang/go#53502 (comment)

This makes sense, if you see them as a more manageable approach to replace directives.

More information https://earthly.dev/blog/go-workspaces/

Checklist

• I have discussed my proposed changes in an issue and have received approval to proceed.
• I have followed the coding standards of the project.
• Tests or benchmarks have been added or updated.
• Documentation has been updated on https://github.com/wundergraph/cosmo-docs.
• I have read the Contributors Guide.

[df-wg]

In general, lgtm. One additional change I'd like to see would be explicit recommendations in Contributing.md, perhaps, about how it's best to configure a personal workspace to make things smooth, if there is any difference from our current workflow

[StarpTech]

@df-wg addressed, thanks.