Release: v0.2.4

[JannikSt]

No description provided.

[Copilot]

Pull Request Overview

This PR introduces version 0.2.4 with a collection of changes that improve provider registration, GPU support, and overall configuration consistency across the codebase. Key changes include:

• Enhanced provider registration flow with staking approval and user confirmation.
• Refactored GPU support by replacing boolean flags with an Option-based GpuSpecs in Docker services, CLI command, and hardware detection.
• Updates to tests, documentation, Cargo.toml version, and CI workflows.

Reviewed Changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
worker/src/operations/provider.rs	Added provider registration control flow with staking and balance validations.
worker/src/docker/service.rs	Replaced boolean has_gpu with Option and updated test configuration values.
worker/src/docker/docker_manager.rs	Modified GPU handling to leverage GpuSpecs and support GPU indices for container start.
worker/src/cli/command.rs	Updated CLI command to extract GPU specs from node configuration.
worker/src/checks/hardware/hardware_check.rs	Adjusted GPU specs collection to handle multiple GPU devices and select a primary GPU.
worker/src/checks/hardware/gpu.rs	Refactored GPU detection to return a vector of devices and aggregate GPU indices.
validator/src/validators/synthetic_data.rs	Added conditional logic for S3 environment variables in synthetic data tests.
shared/src/models/node.rs	Extended GpuSpecs with an indices field and updated testing structures accordingly.
orchestrator/src/api/routes/nodes.rs	Enhanced node API to aggregate status counts along with node data.
discovery/src/api/routes/node.rs	Updated test fixtures to include GPU indices in the node model.
Cargo.toml	Bumped the workspace package version from 0.2.3 to 0.2.4.
CONTRIBUTING.md	Revised contributing guidelines and branch workflow instructions.
.github/workflows/checks.yml	Modified CI workflow to install and configure Redis properly before running tests.

Comments suppressed due to low confidence (1)

validator/src/validators/synthetic_data.rs:646

• [nitpick] Consider adding tests for the scenario when both S3 credentials and bucket name are provided to ensure that S3 integration is properly validated, rather than only logging and returning early.

if s3_credentials.is_none() || bucket_name.is_none() {