[TASK] Reusability of blueprints, generic context/clients

[drewstone]

Overview

Right now our blueprints are not very composable across the Eigenlayer<> Tangle barrier. If you build a Tangle Blueprint, most likely you're using a Tangle context and those functions prevent this blueprint from being composable with an Eigenlayer blueprint.

We would need an protocol / environment agnostic tools that at least we build so that developers can compose the tools we're building with other blueprints.

Example - BlsContext

#[derive(Clone, KeystoreContext, TangleClientContext, ServicesContext)]
pub struct BlsContext {
    #[config]
    pub config: sdk::config::StdGadgetConfiguration,
    #[call_id]
    pub call_id: Option<u64>,
    pub network_backend: Arc<NetworkMultiplexer>,
    pub store: Arc<LocalDatabase<BlsState>>,
    pub identity: ecdsa::Pair,
}

The TangleClientContext, ServicesContext.

Goal
Can we get our primitive blueprints to be environment agnostic?

• As a developer, if I am building with a primitive blueprint I should be able to use it in Eigenlayer or Tangle environments.

P2P generic client (currently MPC context)

• Get operators and keys (generic over the client fetching them

Probably best to implement this inside gadget-workspace as we are migrating to a more organized place where dependencies are feature flag protected.

[Serial-ATA]

It's a lot easier to make generic services now. Job functions can be imported by any blueprint if they are specified in a library, and the environment configuration happens in the binary when creating the runner.