WIP: refactor: split publish from packaging

[caarlos0]

this is the general idea I have for splitting the publishing part.

What we gain with that:

• all the skip publish logic can be done in a single place
• we can have better error handling (packaging vs publishing)

The general idea is:

• artifact types will be basically duplicated (prefixed with something that tells that they can be published)
• the Pipes will be split between building the thing and publishing it
• the publish itself will also be a pipe (like the defaults pipe)

In the future, we may improve this further by having a Packager interface (or something like that), so the pipeline would be:

• defaults
• build
• package
• publish

Any thoughts?

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.