rename this repo to go

[cbrake]

renaming will give us a go import path of:

github.com/simpleiot/go

instead of:

github.com/simpleiot/simpleiot

it is a little shorter and fits in better with the other repo names. This repo is essentially a monorepo of go code that can be used to build both edge and cloud IoT apps, so it seems go is a fitting name for the repo.

Let me know any thoughts, or if this will greatly inconvenience anyone? Now is better than 2 years from now to make this change.

[cbrake]

thinking more -- could archive this repo so it can still be used and simply start a new one -- then nothing should break.

[cbrake]

I've decided to leave as is. The repo includes both frontend and backend code (go/elm), so its not really pure go, and who knows -- we may end up with a different language for the backend some day, so I think simpleiot is the most flexible and descriptive, even though the go imports look a little ugly. But, with goimports integration in editors, most developers don't manually type out import paths anymore.

On gophers slack, I was advised by one person not to use a vanity import url, like many go projects do: