Separate publish

[sbrunner]

Current issue

Currently, we can't update the publishing procedure on stabilization branches because it's too difficult to completely update c2cciutils.

Proposed solution

Create an external project, c2cpublish that only contains the publishing part.

Changes from current implementation

• No automatic detection of packages that should be published.
• Add support for publishing npm packages.
• Remove the non-working Google calendar.
• Create a new configuration file names .github/publish.yaml, move dpkg.yaml from ci to .github folder.
• My default does a notification on the repository itself
• Remove the publishing section from configuration, put the content at root level.
• Change a bit the configuration to me more flexible (repository on nearly all kind of publish, publishing rules on repository)

What didn't change:

• Publishing from the same branch schema
• Publishing of Docker images, Python packages, HELM chart with the same features.

[sbrunner]

@danduk82 Do you agree with that?