Groovy good first issues

This issue proposes adding support for Pixi, a package manager similar to Conda, to Nextflow. The suggested implementation involves integrating Pixi environment setup within Nextflow processes using a `pixi.toml` file and shell hooks.

The `DependencyHandler.kotlin` helper in Gradle currently returns `Any`, which causes issues when attempting to use it with `implementation` configurations that expect a `String` for dependency declarations with additional configurations like `because`. This leads to a type casting error, and the suggested fix is to have `DependencyHandler.kotlin` return a `String` directly.

The user is requesting a console task for Micronaut applications written in Groovy, similar to what exists in Grails. This would enable developers to easily inspect code generated by AST transforms using an AST browser and interactively test Groovy code within the application context.

This issue proposes a minor change to the header comment in the `gradle-daemon.properties` file. Currently, it states '#This file is generated by updateDaemonJvm', but the desired change is to use the qualified task name '#This file is generated by :updateDaemonJvm'. This change is recommended for better clarity, especially when using `org.gradle.configureondemand` to avoid configuring the entire build.

This issue proposes leveraging Shadow's R8 support to reduce the size of the dependency sorter's standalone CLI. The goal is to shrink the current 29 MB binary by enabling R8 for optimization, potentially also improving its performance.

This issue points out a potential inconsistency in the Gradle user guide. The performance section refers to 'aggregate tasks' which might be better described as 'lifecycle tasks' for consistency with other parts of the documentation. The reporter suggests updating the terminology and adding a link for clarity.

The Kotlin DSL documentation incorrectly states that the embedded compiler only supports x86_64 architectures. This information is outdated and needs to be updated to reflect current support for a wider range of architectures.

This issue proposes adding Devcontainer support to the project. Devcontainers offer pre-built, isolated development environments using Docker, simplifying onboarding, reducing local setup friction, and preventing "works on my machine" issues. The suggested implementation involves creating a devcontainer configuration file to manage Java versions, package managers, initialization scripts, and environment variables.