goreleaser: remove snapcraft section

[dmorn]

While goreleaser proved itself as a very effective tool for building github releases, it lacks in flexibility when there is the need to provide a snapcraft package. The idea is to remove the snapcraft section from .goreleaser.yml, and provide a separated snapcraft.yaml for building that type of packages.

I believe that we can do something like what have been done in hugo.

[dmorn]

Maybe it would be better to create a separate repo with all the tools needed to build booster programs. In fact it would be nice to also pack booster's cli together with the main program, but it would be misleading to put the releasing script of the cli here, instead of in it's directory..

[dmorn]

@philipgiuliani what do you suggest? Is this repo a bad idea in your opinion?

[philipgiuliani]

I think the release repo is the correct way to generate a combined binary which includes all of the booster binaries. I like the idea a lot 👍