Workflow - Manually package up deployable folders upon repository release

[AlexVanK]

It turns out that upon a release, GitHub automatically creates binary files and attaches them to the released version. These files are not deployable in the sense that the directory structure and nomenclature doesn't match with the requirements of automatic deployment through Drupal.

Especially the tarball_url and zipball_url that come with the /releases api containt unusable material.

In other words, as is, the provided .zip and .tar.gz files would have to be downloaded by the user, unpacked, renamed, etc. etc. We can't have any of that happening.

It should be possible to automatize this through a GitHub action.

[AlexVanK]

Taken care of in new workflow. Still needs to be documented in wiki