update daisybio profile: use group of the launch directory for work directory

[JohannesKersting]

---

name: daisybio profile update
about: use group of the launch directory for work directory

Our profile creates all work directories in a centralized location. Currently, this work directory will belong to the group of the user launching the pipeline. As a consequence, only this user will be able to use Nextflow's resume feature.

This update sets the group of the work directory (and group special permission) to the group of the launch directory to allow all users in a shared group project to access the work directory and use the resume feature.

Please follow these steps before submitting your PR:

• If your PR is a work in progress, include [WIP] in its title
• Your PR targets the master branch
• You've included links to relevant issues, if any

Steps for adding a new config profile:

• Add your custom config file to the conf/ directory
• Add your documentation file to the docs/ directory
• Add your custom profile to the nfcore_custom.config file in the top-level directory
• Add your custom profile to the README.md file in the top-level directory
• Add your profile name to the profile: scope in .github/workflows/main.yml
• OPTIONAL: Add your custom profile path and GitHub user name to .github/CODEOWNERS (**/<custom-profile>** @<github-username>)

[nictru]

Much needed :D

[JohannesKersting]

Do I need to be worried about the failed github actions?
Don't think they relate to the change in this pull request.

[nictru]

The issue is that the actions are trying to utilize the latest nextflow 24.11-edge, which requires Java 17 or later, but somehow the environment sticks to Java 11

[nictru]

@maxulysse is working on a repo-wide fix similar to this

[maxulysse]

@maxulysse is working on a repo-wide fix similar to this

#813