Remove generated go bindings

Many of the open PRs and issues on this repository have to do with the go bindings. This problem seems generally intractable in an open source environment: we could probably patch up the current issues and add CI to help us keep on top of things, but that only really allows us to support a single version of Go. What about C# or other languages? What about different versions of Go?

We should deprecate the existing bindings and remove them once clients have had a chance to migrate. If we don't want to go all the way to requiring clients to generate their own bindings, one possibility would be to move the bindings to the remote-apis-sdks repo. Not sure if that's viable or not, but it seems like a better fit given that that repo is already an SDK...

Review the issue discussion and the existing Go bindings to understand their current location and client impact. Compare removing them with moving them to remote-apis-sdks, and clarify the migration and deprecation plan before identifying implementation files. Done means the repository has an agreed, documented path for handling generated bindings.

Written by the indexing model from the issue text.