Split the repo in two

[sunker]

It makes no sense to have both frontend and backend code in this repo since they don't share code, settings or version numbers. We should therefore move the frontend code and frontend tooling to a new repo - grafana-aws-sdk-js (or something). The backend code can be kept in this repo, but the repo should be renamed to grafana-aws-sdk-go.

Somewhat related to #27.

[andresmgot]

I think it's not that easy to rename this repo, the golang path would change, causing a breaking change for the packages using this. I think we can leave this repo as it is and move JS code to a different repo.

[sunker]

Yep that's totally fine!

[ryantxu]

I suppose it is fine -- and we are already dealing with a mass of repos, so 🤷‍♂️

the fact that they don't share any code is a bit orthogonal to the fact that both projects are used together. The frontend+backend need to work with and produce objects that work together.

Is there something I am not thinking of that makes this actually better to have managed in two places rather than one?

[andresmgot]

Is there something I am not thinking of that makes this actually better to have managed in two places rather than one?

Replied at #35 (comment).