This is a bit controversial, let me explain the thought process here.
Historically SysOTA started as a project inside the OSTC organization,
hosted on ostc-eu.org. Over time it was associated with the Oniro
project, still managed by OSTC but now at a new in-between domain at
booting.onrioproject.org. It has recently become an Eclipse project and
is hosted at gitlab.eclipse.org (under a rather deep import path).

If you see the pattern, the renames are tedious. We may be a XYZ project
later but, for as long as I'm the project lead, let's use one short and
stable Go import path at gitlab.com/zygoon.

This is further complicated by the Eclipse release process. I cannot
formally release SysOTA at Eclipse myself. This is fine and is well
within the rights of the Eclipse organization to decide. As such
releases will still happen, as Git tags, on the new
gitlab.com/zygoon/sysota repository.

SysOTA is a part of the oniro-core project and does not have a separate
release schedule or life there. Apart from the yearly release cadence,
it's unlikely to get very fast anytime soon, given that oniro-core is an
entire distribution with a lot of code and IP processes to follow.

This is needed for practical reasons. Eclipse release process requires
possibly weeks of overhead to properly plan for, ahead of time, and
later to prepare all the legal paperwork. We may reach a point where we
can "just" release in a matter of a week or two, but we are not there
yet.

As such, let's go to a space without any big brands so that I can git
tag things and not have to feel I'm breaking the rules.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>