[CHECKLIST] Migrate gadget-workspace back into SDK

[drewstone]

Overview

Gadget workspace is being used to rewrite the gadget SDK as separate crates.

• https://github.com/tangle-network/gadget-workspace

Checklist

• [TASK] Generalize MPC, signature blueprints over supported restaking protocol (Tangle / Eigenlayer) #550
• [TASK] Migrate event listeners (consume event-utils since it's minimal) #551
• [TASK] Migrate runners #552
• [TASK] Add misc tangle utilities to gadget-utils-tangle #553
• [TASK] Add misc eigenlayer utilities to gadget-utils-eigenlayer #554
• [TASK] Migrate store (local database) to a new crate #555
• [TASK] Migrate prometheus to metrics directory as separate crate #556
• [TASK] Migrate executor to new crate #557
• [TASK] Support for a network that doesn't rely on rounds-based #558
• [TASK] Docker utils gadget-workspace#27
• [TASK] Remove gadget-io on migration #560
• [TASK] Remove channels logic from networking, then we can feature gate rounds-based compatibility #561
• [TASK] Add tests to keystore gadget-workspace#26
• [TASK] Add tests to networking gadget-workspace#23
• [TASK] Add tests to clients gadget-workspace#25
• [TASK] Test evm event listeners crates #586
• [TASK] Test tangle event listeners crates #587
• [TASK] Test cronjob event listeners crates #588
• [TASK] Migrate macros over, feature gate tangle vs. evm
• [TASK] Migrate the blueprint manager and improve
• [TASK] Remove bytes from runtime and workspace migration [TASK] Remove bytes field type tangle#834
• [TASK] Migrate blueprint build utils
• [TASK] Migrate blueprint metadata (dependent on macros)
• [TASK] Create a library for converting docker compose yaml files to bollard Containers.
• [TASK] Verify the CLI works as expected (create new Tangle / Eigenlayer blueprints) #589

Don't migrate

• Slashing
• Tracer
• GadgetRunner

Questions / considerations

1. What if anything can be considered plugin/extension that doesn't belong in the SDK?
2. Future support for iroh, consensus protocols, kubernetes, TEE support