fix: create jobname with wildcards of all jobs in job groups

[dlaehnemann]

• also use job.groupid instead of job.name for log_folder in case of job groups

This fixes a KeyError on JobGroup that I got, because a JobGroup doesn't have a wildcards_dict property (only its member jobs have that property). So this pull request fixes the plugin, to allow using group jobs without throwing an error.

[dlaehnemann]

@BEFH, any capacity for a quick review? Would be great to get this in and released, so we can avoid having to hack into our plugin installations...

[BEFH]

I don't actually have a CI set up to automatically release on pull request merges, but I will make a release for this shortly.

[dlaehnemann]

As with the main plugin code, I think simply copying from the slurm executor should be easy enough for getting release-please to run... ;)

[dlaehnemann]

So this here:
https://github.com/snakemake/snakemake-executor-plugin-slurm/blob/main/.github/workflows/release-please.yml

[BEFH]

I think there's actually more new code than old in here, but I get you.

I haven't used Release Please in the past, but I may add it soon. I want to make sure there aren't requirements for commit/PR naming, that we can customize the release notes, and that it handles direct commits as well as PRs. Also, the action used in the Slurm executor is deprecated with https://github.com/googleapis/release-please-action as the new one, so there will be some slight differences.

[dlaehnemann]

Ah, yes. I didn't check for the deprecation, but have seen this in another project. So it's probably worth directly using the newer one.

And release-please does assume conventional commits, which may seem like an additional burden. But I do find them useful anyways, and nowadays often use them, even when not necessary (see this PR for example).

And also, of course there's a lot of specific / unique code over here. That's the whole fun of different workflow systems (and plugins), right... 🤯