[Elsa 2.x] Compliance Failure: Unmaintained transitive dependencies ('NetBox', 'Storage.Net') missing source links and license metadata

### Describe the bug

In **Elsa 2.13** (`Elsa.Core` and related modules), the framework relies on transitive NuGet packages authored by `@aloneguid`, specifically **`NetBox`** and **`Storage.Net`**.

The upstream GitHub repositories for these packages have been deleted, privatized, or permanently archived by the author. Furthermore, the published NuGet packages lack accessible source repository links and structured license metadata.

Because of this, enterprise Open Source Software (OSS) compliance, clearing, and Software Composition Analysis (SCA) tools (e.g., Black Duck, FOSSID, Mend, SonarQube) fail automated build and clearing checks.

### Affected Dependencies

- **`NetBox`** (`v2.3.5`+) — Repository deleted/privatized (`404 Not Found`).
- **`Storage.Net`** (`v9.3.0` / related provider packages) — Repository archived/unmaintained.

### Impact

Organizations with strict enterprise compliance rules cannot pass or approve Elsa 2.x builds into production environments due to these unverified third-party binaries.

### Steps To Reproduce

1. Create a standard .Net Frmaework 4.8/ .NET 6 or .NET 8 project referencing `Elsa` (v2.13.x).
2. Run an automated OSS security/compliance clearing tool (e.g., Black Duck or Mend) on the build artifacts.
3. Observe compliance failure flags on `NetBox` and `Storage.Net` due to missing source links and unverified license metadata.

### Expected Behavior

Transitive dependencies should have accessible source code repositories and verifiable open-source license metadata to pass enterprise clearing checks.

### Proposed Solution

We kindly request the maintainers to consider a patch release for the **Elsa 2.x** maintenance branch that:

- [ ] Replaces `NetBox` and 'Storage.Net' packages with some well mainatained packages

### Context

- **Elsa Version:** 2.13

Start by tracing the Elsa 2.x project and NuGet dependency declarations for NetBox and Storage.Net, then reproduce the reported findings with an OSS compliance or SCA tool. Identify compatible maintained replacements and verify their source links and license metadata. Done means Elsa 2.13 maintenance builds no longer pull the flagged packages and pass the relevant compliance checks.

Written by the indexing model from the issue text.