Use tar.gz or tar.bz2 instead of .bz2 for github release artifacts

Hi is there a special reason why you use .bz2 for GitHub release artifacts? While this is technically fine (maybe a bit uncommon but that’s of course not an issue :slight_smile: ) it’s a real pain to handle .bz2 with e.g. Ansible because there is no native module that could handle .bz2 files (see Would it be possible to simply use .tar.gz or .tar.bz2?