Migrate to cdevents org

[e-backmark-ericsson]

This is the overall issue about migrating content from this repo to the cdevents GitHub organization. Once this issue is closed, the migration should be considered done and the division of responsibilities between SIG Events and the CDEvents project should be clearly enough documented.

Since GitHub has no option to track hierarchical issues (except for "tasks") we will group all migration related issues by labeling them with "migrate to cdevents", and thus be possible to list following this link.

Comments on what should be migrated or not should be written in this issue and the actual progress of the migration to be handled in separate issues for each isolated part of the migration.

[e-backmark-ericsson]

There seems to be no way to move GitHub discussions from one org to another, so my proposal on those is to re-create them in cdevents (either in spec or community repo) and have them linked to the discussion items in this repo. There hasn't been much activity on these discussions lately though, so we might not want to continue using GitHub discussions for such discussions? See also this issue.

[e-backmark-ericsson]

The Go SDKs should be decommisioned as there is a new Go SDK being developed under cdevents. See issue #129 .

[e-backmark-ericsson]

The PoC(s) in this repo should be moved to the cdevents org. It currently has two variants in it - one with Spinnaker and one without. Should those be split into two different PoCs? Should we actually have them as PoCs in the cdevents org, or should they rather be "reference implementations"?

[e-backmark-ericsson]

Open issues and PRs in this repo might need to be closed, merged or transferred to cdevents org. Se issue #130